Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

coffee.md file not recognized as literate CS by file ext #173

Open
joehannes-zz opened this issue Dec 26, 2014 · 0 comments
Open

coffee.md file not recognized as literate CS by file ext #173

joehannes-zz opened this issue Dec 26, 2014 · 0 comments

Comments

@joehannes-zz
Copy link

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant