-
Notifications
You must be signed in to change notification settings - Fork 143
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
TagAllOperationsRule #1010
Comments
roxspring
added a commit
that referenced
this issue
Jun 26, 2019
roxspring
added a commit
that referenced
this issue
Jun 26, 2019
roxspring
added a commit
that referenced
this issue
Jun 26, 2019
roxspring
added a commit
that referenced
this issue
Jun 26, 2019
roxspring
added a commit
that referenced
this issue
Jun 26, 2019
roxspring
added a commit
that referenced
this issue
Jun 26, 2019
Merged
roxspring
added a commit
that referenced
this issue
Jun 26, 2019
roxspring
added a commit
that referenced
this issue
Jun 27, 2019
tkrop
added a commit
that referenced
this issue
Jun 27, 2019
…bled-by-default feat(server): TagAllOperationsRule disabled by default
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In-house we're about to have a push on making sure APIs are properly tagged so that Swagger UI docs look good, and are neatly divided up using tags as headings. Consequently, I'm considering contributing a
TagAllOperationsRule
with checks for:CaseChecker
)tags:
section (defining heading order)I'm leaning towards a
MUST
severity in each case but am happy to be argued down. Also happy if folks want it disabled in the default configuration.I'm hoping that this might be accepted into the
ZallyRuleSet
.The text was updated successfully, but these errors were encountered: