Fix validation for Percentage of Max SUV input field in TMTV module #5418
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.
Context
Fixes OHI-2199
The "Percentage of Max SUV" input field in the TMTV module currently accepts any characters (including special characters like +, -, e), which can lead to incorrect segmentation results when the "Run" button is clicked. This PR implements proper input validation to ensure only valid numeric values between 0-1 are accepted.
Link to Devin run: https://app.devin.ai/sessions/47b223d146cc4f2d90e100f8bc9d33cd
Requested by: @sedghi
Changes & Results
Before:
Inputcomponent withtype="text"that accepts any charactersAfter:
Numeric.ContainerandNumeric.NumberInputfrom@ohif/ui-nextmin={0},max={1},step={0.01}Key Changes:
InputwithNumeric.Containercompound componentTesting
To test this change:
Checklist
PR
Code
Public Documentation Updates
Tested Environment
Human Review Checklist: