-
Notifications
You must be signed in to change notification settings - Fork 254
It would be nice to have the option of generating js rather then coffee #46
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
Comments
I think this is an awesome idea for those that can't use coffeescript. I'd love to use backbone-rails but the necessity of coffeescript is putting me off. |
+1 I'm new to backbone and coffeescript so I'd like to start out with just javascript and move to coffeescript later so this would be useful. |
If you use javascript -- and especially if you know Ruby -- you owe it to yourself to look at Coffeescript. |
@dukejones Many of us have looked closely at Coffeescript and still prefer JS. I view Coffeescript as a pointless abstraction with no real added benefit. There is a lot of debate around Coffescript being included by default with rails 3.1, and I am not trying to reignite that debate, but many people share my opinion, and it would be nice to have the option to generate vanilla JS with this great gem. |
I second @sgreenfield; it would be great to have the option to generate vanilla Javascript |
I'm all for this with having coffeescript as the default and an option to generate js instead. Anyone want to work on a pull request? |
I have a pure js fork that I've been using although it's not battle tested. I could create a fork that defaults to coffeescript but allows for a js option unless someone has already tackled this. |
Closing this 10 year old issue! |
This is a great gem; we are not using coffee script though so the generators don't quite fit our needs. Would you be into providing a switch to generate vanilla js rather than coffee?
It seems like the format could be specified as a command line argument and/or configuration setting?
The text was updated successfully, but these errors were encountered: