[275-FIX] Fix for max input values for scale types #288
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For this PR I ended up expanding all the accordions and just blanking all points/weights if two conditions were met
A confirmation alert also shows up currently and prevents scale type switching if it isn't confirmed
An additional update on this PR was changing the way the inputs worked for points/weight to validate their length on blur using
reportValidity
HTML5 validations. This was to prevent being able to temporarily circumvent min and max values by typingPossible alteration to make it more inline with the initial comment if we want would be:
#275