Skip to content

"auto set localesPaths" overrides configurations #578

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

Closed
odex21 opened this issue Jun 1, 2021 · 2 comments
Closed

"auto set localesPaths" overrides configurations #578

odex21 opened this issue Jun 1, 2021 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@odex21
Copy link

odex21 commented Jun 1, 2021

Describe the bug

There is no way to modify localesPaths, they are always overridden by the automatic settings immediately.

Screenshots
图片

@odex21 odex21 added the bug Something isn't working label Jun 1, 2021
@terales terales added this to the Weekly cycle 015 milestone Jun 2, 2021
@antfu
Copy link
Contributor

antfu commented Jun 8, 2021

Can't reproduce on my side. Can you share a minimal reproduction? Thanks

@odex21
Copy link
Author

odex21 commented Jun 10, 2021

The problem with my project looks to have been fixed with 181faa4.
My project is a monorepo, the root directory is identified as a project by the plugin and changes .vscode/settings.json.

But I have no way to undo the plugin's changes, because as long as vsocode is not closed, the plugin will immediately modify the settings file.

Now in a directory that is recognized as legal, as well, localesPaths, there is no way to be set to an empty array or, not set. I think the user should be able to control this behavior of the plugin?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Development

No branches or pull requests

3 participants