104.0.0 ignores settings and changed defaults (?)
See original GitHub issueAfter updating to 104.0.0 plugin started changing my code layout as if I set the settings to these:
{
"svelteSortOrder": "scripts-options-markup-styles",
"svelteStrictMode": false,
"svelteBracketNewLine": true
}
I didn’t have any specific svelte settings set earlier, it just worked. I have tried to overwrite these settings in .prettierrc
, prettier
in package.json
and plain old vs code settings with this config:
{
"svelteSortOrder": "scripts-styles-options-markup",
"svelteStrictMode": false,
"svelteBracketNewLine": false,
"svelteAllowShorthand": true,
"svelteIndentScriptAndStyle": true
}
, but it keeps ignoring me (restarted Svelte plugin, VS Code, Mac).
Not sure what logs I can provide.
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (5 by maintainers)
Top Results From Across the Web
Terminal defaults to powershell ignoring settings #5578 - GitHub
Steps to reproduce. Just open Windows Terminal, and the starting shell is powershell, regardless of "defaultProfile" setting in global ...
Read more >Cannot Change Default Apps - Microsoft Community
Suddenly I cannot change what apps are defaulted to open. 1) I change it in settings, it shows it has changed, but ignores...
Read more >Microsoft Edge Ignoring Defaults!! - YouTube
Are you getting sick and tired of Microsoft Edge completely ignoring your default browser and opening anyway? Well today we are going to ......
Read more >Release Notes | Google Cloud CLI Documentation
Fixed bug in gcloud container fleet and gcloud container hub command groups where a membership with ambiguous location was not given default value...
Read more >Code 2022.3.0 Beta - NVIDIA Omniverse Documentation
Triggers attribute change when animation keys are deleted. It's mainly for OM-39137 to update property window. Setting a key will only ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@dummdidumm I added them to
package.json
.Yes, thanks for the clarifications. I’ll close the issue since the solution to this problem is to specify all the settings for the plugin.
Where did you add them?
.prettierrc
/package.json
? If so - that’s expected behavior. As soon as something is found in a.prettierrc
orpackage.json
those options are used and the options set via the extension are ignored - there is no merge of options. This makes sense because you might collaborate on code where a.prettierrc
is present but not all defaults are specifically listed, but it’s still expected that these defaults are used instead of you local overrides.