-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Implement #3332 #3333
Implement #3332 #3333
Conversation
Whoops, sorry about that! |
Hehe, i knew you'd probably be working on this. At least i hadn't done much to merge #3198 into |
@epidemian Well, something like that was expected. Let me have a look and merge the two together? |
@@ -12,7 +12,7 @@ helpers = require './helpers' | |||
SourceMap = require './sourcemap' | |||
|
|||
# The current CoffeeScript version number. | |||
exports.VERSION = '1.6.3' | |||
exports.VERSION = '1.7.0' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The only reason this is hardcoded is because of the web version, right ?
Instead of doing that, just put Underscore as a |
@jashkenas I'll use |
Oh, you mean
We can probably assume that you have a version of |
|
I'd prefer to stay away from a dependency on eco if at all possible. We don't want to ditch one dead technology in favour of another dead technology. |
I vote for keeping it simple. Failing that, if you're not going to do it with underscore templates, then your best bet is probably ECT. CoffeeKup would be awesome, but it's also not getting much maintenance love. |
Eco is dead (last commit 2 years ago), EJS is dead (last commit in 2009), damn. |
@michaelficarra I'd say this is harmless, eco will work as long as npm keeps its version in the registry. Worse thing is: npm/npm#1341, so you have to manually run |
@Nami-Doc ok, I'll try toffee, at least it's got multiline code blocks. Everything's gonna have the |
Spent a few minutes fork-jumping. Looks like this is under current maintenance: https://github.com/goodeggs/teacup |
Or, instead, you could just stick to Underscore templates (which are about the simplest possible thing for this use case). Having a few lines of JavaScript instead of CoffeeScript at the top of the file is no big deal. And/or you can pull more of the data configuration over into the Cakefile. |
Yeah, seems like my last edit was not submitted. Let's just use the simplest option, underscore templates |
Underscore it is, toffee is troublesome, codeFor will go to Cakefile and codeFor calls with be in JS.
|
Done? |
LGTM 👍 |
Almost there. Maybe only |
@jashkenas Done |
@Nami-Doc I thought last commit of ejs is "2 months ago"? |
@jiyinyiyong oh right, googling it got me on [http://embeddedjs.com/](this website) |
I have intentionally split this up into separate commits, the first one is the actual change from Ruby to Node. Having the whole
_.template
function in Cakefile is not ideal (I cut it down though), but at least doesn't add another dependency. Better solutions welcome.I've done this after three pints, so peer review would be highly welcomed.
Little note: Highlight.js parses object
keys
asattribute
, so I deleted it from thecss
file to keep an equivalent style.Second note: @michaelficarra the
run
expressions are javascript expressions, so we can't use#{}