You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Tools -> Options -> Node.js -> Formatting -> Braces i have "Place open brace on new line after function" and "Place open brace on new line for control blocks " checked.
If i have a function like this:
function SuperDuperFunction()
{
}
Then go to edit format selection / document, it will move the opening bracket to the same line.
function SuperDuperFunction() {
}
Any idea what causes this or how i can work around it?
The text was updated successfully, but these errors were encountered:
hrm... I can't seem to reproduce... What's the build action of the file set to? If it's set to "Compile", then the Node.js formatting settings will kick in. But if it's set to "Content", the JavaScript formatting settings will kick in and you'll have the select the proper setting there too.
See #67 for more info, but this is one of the unfortunate results of having separate language services for Node.js / JavaScript.
The build action is set set to Compile. I tried setting javascript formatting to "Place open brace on new line after function" too. Tried changing between Compile and content, unchecking and checking braces on new line but nothing seems to change. Do you have any other troubleshooting advice?
I am having this issue as well, but with no relation to node.js. I have a JavaScript file marked as “Content” (not “Compile”) and the setting is not respected:
In Tools -> Options -> Node.js -> Formatting -> Braces i have "Place open brace on new line after function" and "Place open brace on new line for control blocks " checked.
If i have a function like this:
function SuperDuperFunction()
{
}
Then go to edit format selection / document, it will move the opening bracket to the same line.
function SuperDuperFunction() {
}
Any idea what causes this or how i can work around it?
The text was updated successfully, but these errors were encountered: