-
Notifications
You must be signed in to change notification settings - Fork 1.1k
feat: add information for extra fields as extensions to openapi specs #10460
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
base: master
Are you sure you want to change the base?
Conversation
Pull Request Test Coverage Report for Build 15955595664Details
💛 - Coveralls |
7b5d640
to
b3ad346
Compare
9d58cbb
to
8b6bebb
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.
Commit should be feat:
instead of fix:
Also 👇
8b6bebb
to
2a0fd04
Compare
@aaqilniz, I think this PR is good to merge once the merge conflict has resolved. I believe you can merge the PR too. :) |
@aaqilniz, looks like there are some merge conflicts. Could you please resolve that? Thanks. |
2a0fd04
to
569ebb9
Compare
Signed-off-by: Muhammad Aaqil <[email protected]>
569ebb9
to
bb52423
Compare
Hi, @dhmlau. I have updated the PR. I think we can merge it now? |
The openapi specs generated do not show information about other attributes of the model property like length, scale or generated, etc. This PR adds those attributes as extensions to openapi specs.
Checklist
npm test
passes on your machinepackages/cli
were updatedexamples/*
were updated👉 Check out how to submit a PR 👈