fix: locked input to a min of "0" for Retries #2777
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.
Why submit this pull request?
What changes will this PR take into?
In the Apisix dashboard, in the inputfield of
Retries
under Services, we cannot set a negative value as of currently it doesn't supports it. Hence the up/down arrows have no function if the value is in the negative range.RE: Primarily we can apply a
visibility: hidden
for.ant-input-number-handler-wrap
, but I think the better way is to not remove thoseup/down
arrows and instead, we can lock the input to a minimum value of 0.Related issues
resolves #2775
Checklist:
cc: @Baoyuantop, @freemankevin