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

Fix potential invalid range exceptions when reading integer nodes #275

Closed
asmaloney opened this issue Jan 10, 2024 · 0 comments · Fixed by #278
Closed

Fix potential invalid range exceptions when reading integer nodes #275

asmaloney opened this issue Jan 10, 2024 · 0 comments · Fixed by #278
Labels
bug Something isn't working

Comments

@asmaloney
Copy link
Owner

This has to do with default values on the prototype nodes when reading (see #246).

#250 fixed it for float nodes.

The same should probably be done for Integer and ScaledInteger.

@asmaloney asmaloney added the bug Something isn't working label Jan 10, 2024
asmaloney added a commit that referenced this issue Jan 11, 2024
…uctors

This means we don't have to add more arguments to constructors like we did with the float node implementation (which was also changed).

When reading, we only call the validation if we actually read in a value for Integer, ScaledInteger, and Float nodes (see E57XmlParser.cpp).

Fixes #275
asmaloney added a commit that referenced this issue Jan 11, 2024
…uctors (#278)

This means we don't have to add more arguments to constructors like we did with the float node implementation (which was also changed).

When reading, we only call the validation if we actually read in a value for Integer, ScaledInteger, and Float nodes (see E57XmlParser.cpp).

Fixes #275
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant