This repository was archived by the owner on Jun 10, 2026. It is now read-only.
This repository was archived by the owner on Jun 10, 2026. It is now read-only.
JSON1006.ValueTooLarge and JSON1008.ValueTooSmall into one ValueOutOfRange rule #142
JSON1006.ValueTooLargeJSON1008.ValueTooSmallThe rule factoring here is not wise. Why is it important to have one rule to detect something is too large and another rule for something that is too small? Does this really help the user? Would they, for example, need two different help topics to clarify this distinction?
We should have created something like 'ValueOutOfRange' and collapsed all this analysis into it.
Opened an issue for this improvement.