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.

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

Closed
roxspring opened this issue Jun 25, 2019 · 0 comments · Fixed by #1013 or #1014
Closed

TagAllOperationsRule #1010

roxspring opened this issue Jun 25, 2019 · 0 comments · Fixed by #1013 or #1014

Comments

@roxspring
Copy link
Collaborator

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:

  • Operations have at least one tag
  • Tag names are Title Case (configurable like CaseChecker)
  • All tags appear in top level tags: section (defining heading order)
  • All tags have a description

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.

zeitlinger 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
Labels
None yet
Projects
None yet
1 participant