-
-
Notifications
You must be signed in to change notification settings - Fork 27
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
Using a shared .stylelintrc.json not in current working directory in user settings of vscode #82
Comments
Would love to have this feature as well ;P |
It would be more handy to have this feature! |
A user-level configuration would be convenient. |
For now, we have the property “"stylelint.stylelintPath" to use the stylelint from other directory like the shareable configuration, is it possible to have the similar functionality so that only one configuration will be needed? Or just I miss anything. Thanks anyway. |
I think this alternative might work, setup a workspace with the root folder the directory with your stylelint config in that folder, then add your other projects as sub-folders, e.g
|
Hi @ntwb, For now, I will get the error message (please see the attachment). Correct me if I take it in a wrong way. Looking forward to your reply! |
Here's a quick test: The files and file tree: .
├── project-one
│ └── project-one.css
├── project-two
│ └── project-two.css
└── stylelint.config.js The root folder has the stylelint config file, in each of the project directories I ran You could also do the same sort of configuration using VS Code Workspaces for something even more advanced |
So I'm facing sort of the same issue. My File-Tree:
|
I think there are better ways to do this sort of thing that don't add more complexity to the extension. One example is the fairly common practice of creating a package with the configurations you want to share and then either linking it to the projects that need to use it or if you work on a team, publishing it as a package and having it as a dependency in your projects. In any case, I think this isn't something we'd want to do in-extension. Thanks for your understanding! |
Say I put the
.stylelintrc.json
in a shareable-config file (all the dependency and requirednode_modules
are there, and this configuration is not in my current working directory) so I can let all my projects use the same version of stylelint and related dependency.Is there any chance to use something like ‘a string of path’ to replace the vscode settings.json
stylelint.config
replace by a.stylelintrc.json
file which is not in current working directory(in vscode user
settings.json
){ "stylelint.config”: “../code/my-sharable-stylelint/.stylelintrc.json” }
The text was updated successfully, but these errors were encountered: