Examples and nonexamples don't seem to honor constraints about blaze_compiler HOT 3 CLOSED

yes thats by design, it is unable to process general constraints (they could be data dependent).

from blaze_compiler.

It would be great if the compiler could validate against a more complex example of data. By including an example/nonexample in the root level, the constraints could be evaluated..? (I haven't really thought about other examples than my current project, so could be wrong here. :)

Another useful way would be to create a new Firebase with test data, and point the compiler to that Firebase for validating. Would that kind of idea be completely out of question?

from blaze_compiler.

Yeah a few people have requested this feature. The real tests for blaze
actually do upload to a test database. I did not think of doing this inline
with the blaze compiler but its a good idea.

On Mon, Dec 22, 2014 at 1:37 PM, Niko Nyman [email protected]
wrote:

It would be great if the compiler could validate against a more complex
example of data. By including an example/nonexample in the root level, the
constraints could be evaluated..? (I haven't really thought about other
examples than my current project, so could be wrong here. :)

Another useful way would be to create a new Firebase with test data, and
point the compiler to that Firebase for validating. Would that kind of idea
be completely out of question?

—
Reply to this email directly or view it on GitHub
#30 (comment)
.

from blaze_compiler.