-
Notifications
You must be signed in to change notification settings - Fork 128
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
enhance no-http-verbs-in-paths with excludedPaths option #1501
Labels
good first issue
Good for newcomers
governance
Issues relating to problems with or requests for API governance/linting/decorating
p3
Type: Enhancement
Comments
Should the name of the option be past tense (excluded) or present tense (exclude)? I see that some options are past tense and some are present ( |
I think present tense makes sense, so |
/assign i will solve this issue. |
@Ayush9026 sure, please go ahead! |
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
good first issue
Good for newcomers
governance
Issues relating to problems with or requests for API governance/linting/decorating
p3
Type: Enhancement
Is your feature request related to a problem? Please describe.
https://redocly.com/docs/cli/rules/no-http-verbs-in-paths/
Invariably, there are going to be false positives. Rather than adding them to the Redocly ignore file (which I tend to use more as an API design debt log) I want to be able to list excluded paths as a rule configuration.
Describe the solution you'd like
Describe alternatives you've considered
Doing nothing and using the Redocly ignore file (but it feels noisy to me).
Additional context
n/a
The text was updated successfully, but these errors were encountered: