Migrate TComponent Inputs to Signals for Better Dynamic Translation

Developers
1

Feels like the TComponent relies on traditional @Input() bindings. This works in most scenarios, but it has limitations when translations need to update dynamically as external state changes (e.g. language switches or translation context updates), especially when using ChangeDetectionStrategy.OnPush.

A potential improvement would be to migrate the component inputs from @Input() to signal-based inputs (input()).

Benefits

  • More reliable dynamic translation updates when external state changes.
  • Reduced dependency on ChangeDetectionStrategy.OnPush and manual change detection.
  • Better integration with Angular’s reactive primitives (computed, effect, etc.).
  • More predictable and maintainable reactive behavior.
2

Hi @Lertis

Thank you so much for reaching out and sharing your thoughts with us. We truly appreciate you taking the time to provide this feedback, customer insights like yours are exactly how we keep improving the Transifex experience.

I will make sure your comments are passed along directly to our product and engineering teams so they can review your suggestions.

Please don’t hesitate to reach back out if anything else comes up or if you have more ideas to share. Thanks again for your support!

Best regards,

Carlos, Transifex TAM

1 Like