Re: [bv-dev] BVAL-192 'exclusive' flag for @DecimalMin/@DecimalMax
> @DecimalMax(value = "0.0", exclusive = true)
Can we name it "inclusive" rather than "exclusive"? Personally I
prefer
positive variable/method names as I think they read better, in particular
when it comes to negation.
I think inclusive also has a clearer meaning, it took me three reads
through to work out what the purpose was. I wondered if Hardy picked
exclusive for a sensible default value, but gave up trying to get my
head around it (newborn baby is my excuse).