could we have an env var for a custom config file path for each linter? #2608
Closed
NicolasMassart
started this conversation in
Ideas
Replies: 2 comments
-
Great request. I am also confused by the conflicting advice between super-linter and spectral on which file to use to make a custom rule set, .openapirc.yml or .spectral.yml. I was going to post a question along these lines, but maybe you could help? Which is it? I have put my changes in both but the rule which I am trying to ignore stills comes up. I am running this in an Azure DevOps CI pipeline. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Please, open a new feature request so we can get more details about this. Thanks! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Some have a file name env, some have none.
I would love the OpenAPI linter (Spectral) to be able to have it's config file name configured because the default one is not even the same default as in the base Spectral (and there's no doc on this, I had to check the code)
Having a variable would then help using our preferred name, including the one that makes sense by the original linter default.
Beta Was this translation helpful? Give feedback.
All reactions