-
Notifications
You must be signed in to change notification settings - Fork 2
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
Issue #44567: Hide scannable option for floating point fields due to improper matching. #695
Conversation
scannable={field.scannable} | ||
appPropertiesOnly={appPropertiesOnly} | ||
showScannableOption={domainFormDisplayOptions?.showScannableOption} | ||
////Issue #44567: Hide scannable option due to matching issues with floating point representation. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm...I'm torn on if these commented out lines should stay in the code or not. I assume the reason to leave them is incase we ever decide to go back on this. I think just putting the issue number comment here is enough as that should lead to the issue tracker which will have the PR link.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I'll leave the comment and make the showScannableOption={false}
explicit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup, that sounds good
Rationale
https://www.labkey.org/home/Developer/issues/issues-details.view?issueId=44567
Hiding the scannable option due to mismatch between floating point representation and expected value
Related Pull Requests
Changes