-
-
Notifications
You must be signed in to change notification settings - Fork 145
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
Allow to set a custom comment for when a result is out of range #2369
Conversation
u"indicate a shoulder range. " | ||
u"Any result outside the results range but within the " | ||
u"shoulder range will raise a less severe alert. " | ||
u"If the result is out of range, the value set for " |
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.
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.
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.
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.
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.
Description of the issue/feature this PR addresses
This Pull Request enables the existing
rangecomment
field, so when has a value set, the system displays that value in results report in accordance. It also makes the default edit form styling to not apply on listings (otherwise, the specs widget is not usable).Current behavior before PR
Is not possible to display a custom text in results report when the result is out of range
Desired behavior after PR is merged
Is possible to display a custom text in results report when the result is out of range
--
I confirm I have tested this PR thoroughly and coded it according to PEP8
and Plone's Python styleguide standards.