Top-level string doesn't interpolate about civet HOT 4 CLOSED

I think it has to do with caching. Since the "civet coffeeInterpolation" prologue directive changes the behavior of strings if it is followed by a string it may be parsed and cached. I'd prefer to not add strings to the non-cached list since that could affect parsing performance throughout the whole file.

Fine tuning the directive prologue parsing to only check for simple strings may fix this.

from civet.

It may be an open question whether we should mangle top level directive prologues. In this case "Hello #{name}!" is parsed as a JS prologue in the spec and probably shouldn't be interpolated no matter what civet config options are specified.

from civet.

Oh, I forgot about JS prologues. This behavior makes sense then, I think.

It might make sense to just clear the cache after parsing the Civet directive, though I'm not sure whether this is ever an issue.

from civet.

I probably need to add a comment in the parser since I forgot about it until reading the code :)

from civet.