{"id":223,"date":"2017-08-20T15:07:06","date_gmt":"2017-08-20T19:07:06","guid":{"rendered":"http:\/\/langstonsoftware.com\/?p=223"},"modified":"2024-01-30T19:09:16","modified_gmt":"2024-01-31T00:09:16","slug":"currency-inputs-in-angularjs-1-x","status":"publish","type":"post","link":"https:\/\/langstonsoftware.com\/2017\/08\/20\/currency-inputs-in-angularjs-1-x\/","title":{"rendered":"Currency Inputs in AngularJS (1.x)"},"content":{"rendered":"
Currency inputs seem to be a forgotten area of standard libraries. Even the batteries included .NET MVC framework doesn’t really answer the question for you.<\/a> They often are omitted completely, and the community variants are many and buggy. This soup of conflicting standards over a very basic problem brings us to the canonical problem: when is it time to write your own solution?<\/p>\n <\/a><\/p>\n AngularJS (1.x) has at least five different easy to find options (links<\/a>. to<\/a>. many<\/a>. options<\/a>. here<\/a>.). Most of them are built off the built in formatters for currency<\/a> or numbers<\/a>. But in my last work project I found most of them unacceptable, at least to the product manager testing the solutions. So I created my own n+1 answer.<\/p>\n