Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Providing invalid config file path should raise instead of silently ignoring it #362

Closed
Sija opened this issue Mar 7, 2023 · 1 comment · Fixed by #393
Closed

Providing invalid config file path should raise instead of silently ignoring it #362

Sija opened this issue Mar 7, 2023 · 1 comment · Fixed by #393
Labels
bug

Comments

@Sija
Copy link
Member

Sija commented Mar 7, 2023

RIght now, it's possible to provide an invalid config file path and ameba just ignores it and uses the default config.
Instead it should raise, and abort the execution altogether.
@Sija Sija added the bug label Mar 7, 2023
@Sija Sija added this to the 1.4.3 milestone Mar 7, 2023
@Sija Sija mentioned this issue Mar 7, 2023
Merged
@Sija Sija removed this from the 1.4.3 milestone May 1, 2023
@jwoertink jwoertink mentioned this issue Jul 11, 2023
Open
@stufro stufro mentioned this issue Jul 24, 2023
Merged
@stufro
Copy link
Contributor

stufro commented Jul 24, 2023

I've created #393 for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Raise error when passed invalid config file path stufro/ameba
2 participants
@Sija @stufro