-
Notifications
You must be signed in to change notification settings - Fork 13
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
chore: new logic for minMax component: min value can be 0 #2611
Conversation
Front-end summary Node 18
|
…type; support negative value for min
…ss getLowerThreshold
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.
Good job!
It seems to behave as expected (still, please check comments), and there seems to be no regressions with this UI component (though I checked only a couple of interactions).
In published test, score is calculated, and seems like it's correctly limited to upperBound/lowerBound
(with negative and or/float numbers)
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.
Works well, good job!
- New code is covered by tests (if applicable)
- Tests are running successfully (old and new ones) on my local machine (if applicable)
- New code is respecting code style rules
- New code is respecting best practices
- Feature is working correctly on my local machine (if applicable)
- Acceptance criteria are respected
- Pull request title and description are meaningful
Version
There are 0 BREAKING CHANGE, 0 feature, 7 fixes |
Related to: https://oat-sa.atlassian.net/browse/AUT-1389
Separate zero and disabled states in minMax component
Changes:
Nagranie.z.ekranu.2024-11-7.o.16.27.50.mov