-
Notifications
You must be signed in to change notification settings - Fork 156
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
Add settings-path
option support
#63
Comments
@sobolevn hi! Sorry for replying so late! 🙇♂️ I'm ok on adding that option, though I would be great if we could get that from isort itself, would that be possible? 🤔 Anyway, with your current proposal:
Sounds reasonable? 🤔 |
Hello @gforcada, is this planned? I can take a shot at implementing this |
@GideonBear not from my side, I would welcome a PR though 👍🏾 |
Alright, I'll take a look, thanks for the quick reply! |
@GideonBear there you are, let me know if you need help 😄 |
Will do, thanks! |
@gforcada The plugin is broken on master: |
The docs say: def parse_options(option_manager, options, args):
pass
# or
def parse_options(options):
pass |
Yes,, a test like that would be great, you are welcome to write it if you have the time and skills 👍🏾 |
There's an awesome setting for the
isort
that I use quite frequently in my setup:settings-path
.It allows to specify the desired configuration path.
Could I please add a support for this option to this library?
I really miss it, and it won't interfere with nay other options.
That's how I think it should work:
--no-isort-config
is passed, then we ignore all other steps and use the default options0.1 We can also raise an exception if both
--no-isort-config
and--isort-settings-path
are passed0.2 We can just ignore the
--isort-settings-path
1.1 We can raise an exception. All
flake8
check will fail with this exception. This will help to indicate about the problem early1.2 Just fallback to the config finding behavior in case this file is missing
@gforcada What do you think?
I personally prefer explicit exceptions. As they indicate about the problem. And not hiding it.
The text was updated successfully, but these errors were encountered: