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

BREAKING CHANGE: argument + default types should be string #95

Merged
merged 2 commits into from
Oct 27, 2017

Conversation

marcoscaceres
Copy link
Member

No description provided.

@marcoscaceres
Copy link
Member Author

It's weird that the this had not been caught earlier.

@marcoscaceres marcoscaceres changed the title BREAKING CHANGE: argument type should be a string BREAKING CHANGE: argument + default types should be string Oct 26, 2017
Copy link
Member

@saschanaz saschanaz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can do this in non-breaking way but if we don't have an important reason to keep the number type field, this should be okay.

@gsnedders
Copy link

What was the reason for this change? How should I get the value as a JS Number primitive? Is there any danger in doing 1 * ret.value as was done before?

Perhaps most vitally, given a value that isn't representable as a JS Number, does the rounding happen in the right way to match what would happen with a const in a browser?

gsnedders added a commit to gsnedders/web-platform-tests that referenced this pull request Nov 5, 2017
gsnedders added a commit to gsnedders/web-platform-tests that referenced this pull request Nov 5, 2017
@saschanaz
Copy link
Member

What was the reason for this change?

This is because of #94, where the parsed result does not provide the original number literals. 1 * ret.value should give the exact same value as the one previously provided.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants