This repository has been archived by the owner on Aug 31, 2023. It is now read-only.
--config-path support for autofix settings #4780
seang
started this conversation in
Suggestions
Replies: 1 comment 1 reply
-
Hi! Thanks to bring it to light! This should solve your problem. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi!
Our project is using Rome ( loving it so far by the way🙏 ) but we've been running into a weird case with autofix on save.
Recently many of us have been running into workflow issues with the noUnusedVariables rule while working locally. This is something we need to enforce at a higher level but while using the VSCode extension configuration
There is no option to configure it further. We have a dozen other invocations of Rome commands that benefit from the default config file location - so it's counterintuitive for us to pass a --config-path to each of them just so the quick fix extension on VSCode can behave differently than our pre-push scripts for example which need to be more strict.
A simple change would be to allow us to declare the location of a configuration file for the quickfix command to use - so we could isolate specific requirements.
Beta Was this translation helpful? Give feedback.
All reactions