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 a monorepo with a .stylelintrc.yaml in a subdirectory I'm getting errors from my editor integration because this plugin resolves files relative to working directory instead of relative to the config file. I'd suggest to always resolve paths relative to the config file. This is how pretty much all other linters work too.
In case this suggestion is not possible, you could introduce a <rootDir> option like jest also has, e.g. <rootDir>/style.css to specify the path relative to the config file.
The text was updated successfully, but these errors were encountered:
Yes indeed. But until then, this nice plugin is unusable for me 😢. If stylelint plugins have access to the config file path where the plugin's options are set, it shouldn't be too hard of a feature to add.
I guess I will go another route and just pass absolute paths to the plugin. This means I have to migrate my config from yaml to js, but that will be worth it anyways.
In a monorepo with a
.stylelintrc.yaml
in a subdirectory I'm getting errors from my editor integration because this plugin resolves files relative to working directory instead of relative to the config file. I'd suggest to always resolve paths relative to the config file. This is how pretty much all other linters work too.In case this suggestion is not possible, you could introduce a
<rootDir>
option likejest
also has, e.g.<rootDir>/style.css
to specify the path relative to the config file.The text was updated successfully, but these errors were encountered: