Closed dudo closed 2 years ago
Still playing with this one - and learning a little coffescript.
Want me to update these conflicts, or are you over it? lol
Actually what I have been meaning to do is to create a separate Coffeescript branch. That way if people want to use Coffeescript all your hard work is there and they can just pick it up. But when I thought about putting it in the master branch I decided that since it's not my main way of operating and the fact that some code would be regular JS and some Coffeescript it just added complexity. Then I got the branch idea because I don't want to lose the work you did. What do you think?
Best Regards, Dan
On Oct 1, 2014, at 10:51 AM, Brett Dudo notifications@github.com wrote:
Want me to update these conflicts, or are you over it? lol
— Reply to this email directly or view it on GitHub.
So, I replaced controllers/user.js
and models/User.js
with their coffee counterparts. Those don't actually have to be merged, they were really just there as proof of concept.
This PR only really addresses 3 files, app.js
, gulpfile.js
, package.json
. As for giving users an option... everything you have in js would still work fine, and any files written by the user (in js or coffee) would, presumably, be fine as well. So, this is just about making skeleton a bit more flexible out of the box, not to force anything onto the user. I also wouldn't want them to have to choose a branch, and scare them into thinking they had to write all their code in just coffee or just js.
Does that make sense?
Yep - I will create a branch and push it up. I am leaving on vacation tomorrow for a week though and will have limited access. Thanks for pushing this again!!
we may want to add a gitignore to the js files that the coffeescript generates (which means we'll have to put it in another location other than public/js. your call on that.