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.
It looks like the current code that checks bounds for a cvar will fail in two cases.
1st case
If we define min value that is higher than max value and max value is set to false,
it will print -> The maximum value can not be below the minimum value
2nd case
If we define max value that is lower than min value and min value is set to false,
it will print -> The minimum value can not be above the maximum value
Solution
I think first we should check them if they are defined (both are set to true), then we can compare them. (Like I did in the this PR)