-
Notifications
You must be signed in to change notification settings - Fork 453
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
Switch to using coffee-fmt package for beautifying CoffeeScript #192
Comments
Actually it seems that you support CoffeeScript but I do not see any specific options for it in the settings. |
A really good feature would be to be able to activate/desactivate a specific file format. For instance this plugins https://github.com/atom/language-coffee-script seems to handle coffeescript better. Cheers |
CoffeeScript beautification support comes from https://github.com/derekchiang/Coffee-Formatter which is unfortunately not actively maintained. I am open to any alternatives.
That supports CoffeeScript beautification? |
@Glavin001, @shprink I've been working on an npm module for coffee script reformatting, (like changing tabs to arbitrary # of spaces or vice versa). It's built on top of coffee-scripts own tokenizer (which is still pretty ambiguous). Still very much beta, but it does at least transform the above docblock correctly. Maybe you guys could check it out see how it performs. |
Great @sterpe ! I would love to support this and switch from Coffee-Formatter to your Coffee-fmt. Let me know once you think it's at an acceptable state for switching over and what the Node API is that I can use (see https://github.com/Glavin001/atom-beautify/blob/master/lib/langs/coffeescript-beautify.coffee ). Thanks! |
Hey @sterpe, what is the status of coffee-fmt? If you are confident that it can replace Coffee-Formatter than I can support that. Let me know what you think 😃. |
Published to v0.26.0
|
Hi,
Your plugin do not support CoffeeScript but still format it when saving (On save enabled).
it screws my doc block:
to this:
When your plugin is disabled it is fine.
Thanks
The text was updated successfully, but these errors were encountered: