-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Beautifying TypeScript adds extra spaces #555
Comments
As noted on the other bug, Typescript isn't really supported by the js-beautifier. But it's good to have this on the list. Thanks! |
Similarly, for type annotations by flow:
gets turned into
but should remain unchanged. |
@stuhlmueller - Please file your comment as a new issue. If we get around to implementing it, it won't be as part of fixing this issue. |
Any update? |
@bitwiseman what's the status of these fixes? |
@bitwiseman should typescript be its own folder? |
@wbhob - The process of moving to having separate that inherit from javascript is starting, but it isn't there yet. For now, I'd suggest updating the Javascript language instead. I'd suggest doing point-wise changes: pick one feature of TS/Flow and make that change with tests and commenting, finish a Pull request with that change, then pick another feature and so on. That will make it easier to review the changes and reduce the complexity of debugging any issues. |
Although beautify is for javascript, it's very useful for formatting TypeScript, but it does tend to add a lot of extra white space.
For example:
and generics:
The text was updated successfully, but these errors were encountered: