"Bug: 4 Unexpected situation in type system on 'undefined'" should instead bubble up better error messages. about blaze_compiler HOT 5 CLOSED

Hmm. Sorry I missed this alert coming in. ! is not being coerced is the underlying bug. I'll try and work out how to connect these error messages

from blaze_compiler.

Oh ! is special syntax in YAML. So having it in the front of a string causes problems. So you can quote it
"isValid(): "!prev.foo""

from blaze_compiler.

Ok that type of error message is quite hard to propagate as its really a syntax exception in the YAML layer.

from blaze_compiler.

I'm getting the same error message when I call a function that in turn calls another function that is not defined. Reopen?

from blaze_compiler.

There are in fact a bunch of errors that are really difficult to track down when using blaze - $variables must be identically spelled in declaration, rules, and function use, for instance, or they'll silently be eaten.

A big +1 to a sprint spent on making blaze more helpful when compilations errors or mis-matches occur!

Here, we've almost decided to ditch it and just go to straight rules.json, even though they're hideously complex for our setup. Blaze is just really hard to debug, and there aren't many indications of the magic.

If we had it to do again, that's what we'd have done.

from blaze_compiler.