Mastering complex reactivity with template-driven forms and Signals by Brecht Billiet

Master complex reactivity with template-driven forms and Signals, simplifying logic and making it more readable, reusable, and testable with Angular.

Key takeaways
  • Template-driven forms are created over time and can be quite complex.
  • They have a huge amount of logic inside them, which can be challenging to maintain.
  • Template-driven forms are still the most widely used form type in Angular.
  • The author suggests using template-driven forms with signals for better reactivity and maintainability.
  • Signals are a great way to simplify complex logic and make it more readable.
  • A signal is just a simple function that can be executed to update a form.
  • Signals can be used to decouple complex logic and make it reusable.
  • A view model is a reactive object that is specifically tailored for a template.
  • View models are declarative and can be used to make complex logic more readable.
  • The author recommends using a view model to make form logic more declarative.
  • Template-driven forms with signals are a great way to simplify complex form logic.
  • The author suggests using the sc-input wrapper to simplify form logic.
  • Signals can be used to create reusable form logic that is easy to understand.
  • Using signals with template-driven forms can help to eliminate boilerplate code.
  • The author recommends testing signals with a jest mocking library.
  • Signals can be used to create state management and can be easily tested.
  • The author suggests using the vest suite to simplify form validation.
  • The vest suite is a reactive form validation library that is easy to use and test.
  • The author recommends using the nest library to generate nested objects in a form.
  • The author suggests using the rxjs library to simplify form logic.
  • The author recommends using the angular Ivy renderer to improve performance.