-
Notifications
You must be signed in to change notification settings - Fork 121
Description
I'm sorry I can't give you a test scenario.
What I can tell is:
The compiler bails out (even with 0.12.0) with file unknown & unexpected indentation
Strange thing is: it happens with the second file it compiles only, the first one works, though it also is a coffee.md ... so I don't really understand the rootcause ...
Anyway, since I got no pure CS, but literate CS only, I tried adding || ".coffee" to the isLiterate function in the coffee-task -> et voila, no more error, grunt flow right through like a charm.
|| ".coffee.md" didn't work either, so my guess was that the file extension thingy actually doesn't recognize the double dotted file ext correctly.
One interesting fact maybe as well:
It started happening when I added a grunt-shell task that copies the same file.
Hmmm, actually, I got a sceanrio that would make sense right now:
The file ext checker you are using is looking for a max of two dots ... or rather interpreting the first two dots and its postfixes as the file ext....
I got:
ServerConfig.production.coffee.md
ServerConfig.dev.coffee.md
ServerConfig.coffee.md
You see what I mean?
(I am actually having a grunt task using grunt-shell copying depending on the build target the right vars, because I'm using a separate sails server for local testing (quick api setup) ... and I can't share the ports ... this was my quick approach of using grunt && sails in parallel)