-
Notifications
You must be signed in to change notification settings - Fork 12
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
Review Handling of Special Constants, Field Formats, and High Priority Bug Fixes #832
Comments
Hi @jordanpadams @jmafi Special_Constants is on my list of "things to raise with DDWG" so before we make too many changes to validate, I think a discussion is needed here, in particular wrt how we handle IEEE754 data + special constants... |
If I understand #816 and #817 correctly, then check_format() needs to change its error if field or validation format and all errors in this function need to have error/warning counterparts. Leave the message the same otherwise I hope. Correct? |
@al-niessner correct. right now we are treating all precision the same. We need to know not just that there is a precision value, but whether or not it is exact precision (validation_format) vs. max precision (field_format). So I think the current check here should be a warning for |
All sub-tasks completed. Closing out |
💡 Description
It appears we have some improvements needed for handling of special constants and field formats according to the standards and what errors/warnings/info messages should be output to to the user.
👶 Child Tasks
validation_format
#817field_format
#816data_type
before checkingSpecial_Constants
#837The text was updated successfully, but these errors were encountered: