You can clone with
HTTPS or Subversion.
Much comfortable than creating another rule just because it checks exclusively.
So the inRange validator with options lower set to 5 and upper to 10 in exclusive mode should match 3 and 11 but not 7?
Thanks for your explanation. I don't see a why you can't achieve this by specifying lower 6 and upper 9 when it does what you want. Seems clearer to me, wouldn't require reading about/documenting an additional feature and is more straightforward. I'm closing this for now, anybody who has a stronger feeling about implementing this can reopen the ticket.
Couldn't the issue @threestan is seeing be resolved by instead switching the isRange validator to be inclusive all the time?
@threestan I don't think this is common enough to warrant patching the core. What's wrong with just adding a custom validation rule in your app?
Sure, I did so.
IMHO inclusive is the expected behavior
Finally getting caught up here. @threestan I'm fine with inclusive being the default behavior here. If you're willing to provide a patch and a test case in a PR against the dev branch, we'll get it into core.
Warning BC Break: Validator inRange is now inclusive. close #84