You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to suggest an enhancement for the monetary input component of your library. Typically, monetary values are stored as integers, representing the smallest unit of a currency (like cents in the case of dollars or pence for pounds). This approach helps in avoiding floating-point precision issues.
Suggestion:
It would be highly beneficial if the component could automatically handle the conversion of entered monetary values into their integer representation. This feature would streamline the process of handling monetary inputs, ensuring that values are accurately and consistently stored in their smallest unit format.
Example:
When a user enters a value like $10.25, the component would automatically parse and convert this into 1025.
The text was updated successfully, but these errors were encountered:
@Arthur-Carbonari Unfortunately, the author of this library is not developing new features #169 (comment). I think the fastest way would be to do it yourself and open a PR. The author promised to pay some attention to the release of new versions.
Hello,
I'd like to suggest an enhancement for the monetary input component of your library. Typically, monetary values are stored as integers, representing the smallest unit of a currency (like cents in the case of dollars or pence for pounds). This approach helps in avoiding floating-point precision issues.
Suggestion:
It would be highly beneficial if the component could automatically handle the conversion of entered monetary values into their integer representation. This feature would streamline the process of handling monetary inputs, ensuring that values are accurately and consistently stored in their smallest unit format.
Example:
When a user enters a value like $10.25, the component would automatically parse and convert this into 1025.
The text was updated successfully, but these errors were encountered: