-
Notifications
You must be signed in to change notification settings - Fork 1
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
1.5.1 issues #4
Comments
For what plugins you want to activate, just change your I have 5 plugins activated: {
"plugins": [
"esformatter-braces",
"esformatter-collapse-objects",
"esformatter-dot-notation",
"esformatter-literal-notation",
"esformatter-quotes"
]
}
|
It doesn't appear that the extension is formatting my JavaScript files anymore 1.5.1. The results I was seeing appear to be from VS Code's default JavaScript formatter. I get the same results if I uninstall Is there a log somewhere or something I can do to figure out why the extension isn't being used when I format document? The Output tab is empty when I select Extensions. |
Seems the dependency Let me report it to |
@langdonx issue fixed, Please give a try with |
Looking good, thank you! |
With the release of 1.5.1, I've run into 2 issues:
Empty functions get a space put into their body:
1.
const a=function(){};
->const a = function () { };
2.
const b=()=>{};
->const b = () => { };
1.5.1 actually would force a break on the empty arrow functions (fixed in esformatter, but sadly not released).
The
whiteSpace.after.FunctionReservedWord: 0
setting is seemingly ignored:You can see it in the above example, but:
go(function(){});
->go(function () { });
I'm assuming these are because of
esformatter-curly
? Are there options available to stop the extension from using this plugin?The text was updated successfully, but these errors were encountered: