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

Review Handling of Special Constants, Field Formats, and High Priority Bug Fixes #832

Closed
jordanpadams opened this issue Feb 20, 2024 · 4 comments

Comments

@jordanpadams jordanpadams changed the title Review Handling of Special Constants and Field Formats Review Handling of Special Constants, Field Formats, and Content Validation Feb 20, 2024
@jordanpadams jordanpadams changed the title Review Handling of Special Constants, Field Formats, and Content Validation Review Handling of Special Constants and Field Formats Feb 20, 2024
@jordanpadams jordanpadams added B15.0 and removed B14.1 labels Feb 20, 2024
@github-project-automation github-project-automation bot moved this to Release Backlog in B15.0 Feb 20, 2024
@jordanpadams jordanpadams added theme and removed task labels Feb 20, 2024
@msbentley
Copy link

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...

@al-niessner
Copy link
Contributor

@jordanpadams

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?

@jordanpadams
Copy link
Member Author

@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 field_format, but we need an additional check for not equal for validation_format

@jordanpadams
Copy link
Member Author

All sub-tasks completed. Closing out

@github-project-automation github-project-automation bot moved this from ToDo to 🏁 Done in EN Portfolio Backlog Jun 1, 2024
@github-project-automation github-project-automation bot moved this from Release Backlog to 🏁 Done in B15.0 Jun 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 🏁 Done
Status: 🏁 Done
Development

No branches or pull requests

3 participants