-
Notifications
You must be signed in to change notification settings - Fork 42
lint configs should be relative to repo root #31
Comments
How do we want to handle this? Maybe .imhotep-pluginname.conf at the root of a repo? |
Ahh. Maybe. I was actually thinking this meant "hey, go look for my
|
A few of the linters actually support this natively, but I would like to provide an override method. We can inspect the names of the classes and look for files that match the name of the classes in a checked out repo. I can pass a kwarg that has a absolute path to a config file to the tool. It should not break existing modules. |
@scottjab can you provide a link to one? |
https://github.com/bbatsov/rubocop supports an override. |
Ahh, yes. Most do, but our tools don't yet pass them (or discern if they're
|
I think I will take a crack at this tomorrow at pyladies. |
Awesome. Thanks. This is the last big ticket for me, FYI.
|
right now, you have to specify them relative to where you run it, which is silly.
The text was updated successfully, but these errors were encountered: