-
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
Consider using "prettier" for JS and JSX #1497
Comments
Strongly recommend |
Pull Requests welcome! 👍 |
It would be brutal! |
Atom-Beautify will be coming to VSCode! See https://github.com/Unibeautify/vscode |
Thank you Glavin! |
@Glavin001 / @york-xtrem I can give this a shot if no work has started. @Glavin001, should I just fork off |
@utilityboy I finally adopted the environment https://www.jetbrains.com. It has everything I need and everything works well at first with great support! Neither Atom, nor visual studio code, nor Sublime, nor anything ... |
@utilityboy You should check out the future of Atom Beautify at https://github.com/Unibeautify/ The goal is to get beautifiers in as many editors as possible. We could use a bunch of help as there is a lot of work let to do. Here is an over simplification of necessary tasks:
At this time the maintains of JS Beautify and Pretty Diff are collaborators on Unibeautify working hard to achieve this vision. The guys behind Prettier have expressed great interest in this, as well, but there is still a lot of work to do. If you want Prettier to be available to many various code editors I would suggest enhancing Prettier to support the Unibeautify parse-framework and working through their unit tests. Currently Prettier uses Babel and Flex for their parsers. |
just to add, typescript users recommend prettier too |
Prettier will be included in Unibeautify! https://github.com/Unibeautify/beautifier-prettier 🎉 |
https://github.com/jlongster/prettier
The text was updated successfully, but these errors were encountered: