Create new enforce_value_in_range config option, disable by default #16
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.
I've started using bar-card to display the temperature of my house and the desired minimum and maximum temperature. This does, however, mean that the temperature can be outside this range until the house has heated/cooled enough. Because bar-card automatically forces the value to be within the minimum and maximum, this breaks my use case. This small patch fixes it.
I've also disabled this old behaviour by default, because I assume people will generally want to see the real value unless they explicitly mention to want it post-processed to always be within min and max. If you disagree, I'll change the default back to match the old behaviour by default.
Before (true value hidden):

After (true value shown):
