fix: Fix comparison operator for numeric values #8953
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.
PR Description
I noticed that the script was using
==
to compare two numeric values in the conditional statement, which is typically used for string comparisons in bash. For numeric comparisons, it's more appropriate to use-eq
. I've updated the conditional to use-eq
instead of==
, ensuring that the comparison works as expected for numbers.Here’s the change:
==
with-eq
in the comparison:This update ensures that the comparison is treated correctly as a numerical one, preventing potential issues in certain scenarios.
Documentation
doc-change-required
label to this PR if updates are required.Changelog