Numerical constraints about blaze_compiler HOT 4 CLOSED

Hi Thorben, your constraint is correct. The inline testing doesn't cover
arbitrary rules in the "constraint" field, as some of those constraints
depend on previous data and there is no way of currently specifying that.

That said, numeric ranges are such a common constraint I think they deserve
to be expressed in the schema language and tested inline as well. So I will
implement this post haste, but for now your system works but the inline
testing framework is not powerful enough to detect it (there is an open
issue on making that more powerful as well).

Tom

On Thu, Aug 28, 2014 at 8:58 AM, Thorben Schröder [email protected]
wrote:

Hey, is there no way to define numerical constraints (e.g.: must be
between 1 and 999)? I've tried this minimal rule set but blaze tells me my
0 nonexample passes :/

schema:
definitions:
price:
type: number
constraint: next > 0 && next < 100000 # between 0
examples:
- 1
- 1000
- 99900
nonexamples:
- 0
- 100000
- 1000000

type: object
properties:
prices:
type: object
$priceId: {$ref: "#/definitions/price"}

Is that just not possible at all?

Thanks!

Thorben

—
Reply to this email directly or view it on GitHub
#13.

from blaze_compiler.

Hey, thanks for the quick clarification. I'll just comment the examples out for now. And btw, keep up your amazing work. I've last edited Firebase security rules about a year ago and Blaze is sooooooo good! Thanks 👏

from blaze_compiler.

ok you can set ranges now (with testing), explained here: https://github.com/firebase/blaze_compiler#ranges

from blaze_compiler.

Works like a charm!

from blaze_compiler.