Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

property assignment number conversion #80

Open
quarkus opened this issue Jan 30, 2023 · 0 comments
Open

property assignment number conversion #80

quarkus opened this issue Jan 30, 2023 · 0 comments
Assignees
Labels
question Further information is requested

Comments

@quarkus
Copy link
Contributor

quarkus commented Jan 30, 2023

Question / Problem.

if a property is assigned with a value "200.000" the property value will be: 200
if a property is assigned with a value "200.001" the property value will be: 200.001

This is perfectly in line with

parseFloat('200.000') -> 200
and
parseFloat('200.001') -> 200.001 (200 plus a fraction)

I don´t know if we can / should actually do something about it, but this feels pretty weird .. maybe we should parse to number as agressive as we do !?

In distinct case there was a number passed to an attribute "count" (200000) than formatted (via Numberformatter) for decimal delimiter and being reassigned to the same prop.
At the end count has a value of 200 which is logical but still weird ..

@quarkus quarkus added the question Further information is requested label Jan 30, 2023
@quarkus quarkus self-assigned this Jan 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant