I am working on a project where users are expecting to enter numbers in where decimals matter. If the user enters 1.000 we expect to persist 1.000. We use Angular and and leverage template-driven forms. What we discovered is that NgModel does not emit the full number – it always truncates. So even though a user entered 1.000, only 1 is emitted. If a user enters 1.0001 we see the correct value.

I am working on a project where users are expecting to enter numbers in where decimals matter. If the user enters 1.000 we expect to persist 1.000. We use Angular and and leverage template-driven forms. What we discovered is that NgModel does not emit the full number – it always truncates. So even though a user entered 1.000, only 1 is emitted. If a user enters 1.0001 we see the correct value.

I am working on a project where users are expecting to enter numbers in where decimals matter. If the user enters 1.000 we expect to persist 1.000. We use Angular and and leverage template-driven forms. What we discovered is that NgModel does not emit the full number – it always truncates. So even though a user entered 1.000, only 1 is emitted. If a user enters 1.0001 we see the correct value.

I am working on a project where users are expecting to enter numbers in where decimals matter. If the user enters 1.000 we expect to persist 1.000. We use Angular and and leverage template-driven forms. What we discovered is that NgModel does not emit the full number – it always truncates. So even though a user entered 1.000, only 1 is emitted. If a user enters 1.0001 we see the correct value.

In Angular, we have two powerful approaches to building forms: the traditional element with ngModel and reactive forms with FormControl, FormGroup, and FormBuilder. While reactive forms offer advantages like improved testability and separation of concerns, there might be situations where the simplicity of the element is preferable.