JSPrettier inheriting wrong config
See original GitHub issueUsing the latest version of JsPrettier released a couple of hours ago, the plugin now inherits a config from an ancestral directory rather than the one at the root of my project. Eg:
/foo/.prettierrc
is getting implemented.
/foo/bar/baz
is my project root (and Sublime workspace)
/foo/bar/baz/prettier.config.js
is being ignored/trumped by the ancestral config.
Using all default plugin settings, except have toggled auto_format_on_save
to true
.
Issue Analytics
- State:
- Created 4 years ago
- Comments:12 (3 by maintainers)
Top Results From Across the Web
JsPrettier should always use html parser for .svelte file - GitHub
I have tried allow_inline_formatting: false and getting the same behaviour as described above. .svelte file, as of prettier 1.17.1, doesn't have ...
Read more >How to properly re-configure JSPrettier after an update with a ...
When I open the console to see what the error is it says: The system cannot find the path specified. (CR). The settings...
Read more >JsPrettier - Package Control
The Prettier config file is resolved by first checking if a --config </path/to/prettier/config> is specified in the additional_cli_args setting, then by ...
Read more >I don't like prettier : r/javascript - Reddit
My only complaint about the vscode Prettier plugin is that there doesn't seem to be a way to have it enabled only for...
Read more >Formatting | Vetur - GitHub Pages
You can choose each language's default formatter in VS Code config, ... These two settings are inherited by all formatters: ... useTabs": false...
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
Hi @ryami333. JsPrettier performs Prettier config resolution in order to support auto-formatting only when Prettier config files are discovered.
This feature was intro’d back in February of 2018, so I’m going to assume the issue you’re having now is coincidental.
Did you restart Sublime Text after the update from Package Control?
Have you tried tried re-installing the plug-in? Maybe something was corrupted while updating.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.