-
Notifications
You must be signed in to change notification settings - Fork 90
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
feat: operationId should conform to naming convention #124
feat: operationId should conform to naming convention #124
Conversation
Codecov Report
@@ Coverage Diff @@
## master #124 +/- ##
=======================================
Coverage 92.65% 92.65%
=======================================
Files 56 56
Lines 2055 2055
=======================================
Hits 1904 1904
Misses 151 151 Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great, just asking for one small change that I think makes the code more readable
src/plugins/validation/2and3/semantic-validators/operation-ids.js
Outdated
Show resolved
Hide resolved
Co-Authored-By: Dustin Popp <dpopp07@gmail.com>
d83f555
to
ce648a3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! 👍
Make sure you squash the commits and use the feat
commit header to trigger a release
I approved it but now noticing that Travis builds are failing - make sure you get those sorted before merging! |
# [0.17.0](v0.16.2...v0.17.0) (2020-01-29) ### Features * operationId should conform to naming convention ([#124](#124)) ([79ca9b8](79ca9b8))
🎉 This PR is included in version 0.17.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
documentation for operation Id naming convention
We should add support to the validator to check for conformance to these conventions and report any non-conformance as a warning
This PR takes the following approach to check for operationId naming convention:
p
for whichp
andp/{param}
exist,p
has a GET and POST path, andp/{param}
has a GET, a DELETE, and a POST or PUT or PATCH.p
starts with "list"p
starts with "create" or "add"p/{param}
starts with "get"p/{param}
starts with "delete"p/{param}
starts with "update"