-
Notifications
You must be signed in to change notification settings - Fork 18
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(converter): add Reference Object summary and description plugins #3885
Conversation
...c/strategies/openapi-3-1-to-openapi-3-0-3/refractor-plugins/reference-summary-description.ts
Outdated
Show resolved
Hide resolved
@tekyu there is an option to have this plugin divided into two. One plugin that removes summary, one that removes description. The idea is that every plugin just handles one aspect of the the transformation. In this particular case, we can say that the aspect is to remove the non-supported fields, or we can divide the aspect into two separate ones. Please let me know what you think. |
@char0n if the idea is to have plugins that handles single operation I don't want to disrupt that with my plugin. I'll split them then |
@tekyu it's your decision, as for this particular one I don't have strong opinion. |
9b67ab6
to
f942461
Compare
...erter/src/strategies/openapi-3-1-to-openapi-3-0-3/refractor-plugins/reference-description.ts
Outdated
Show resolved
Hide resolved
...converter/src/strategies/openapi-3-1-to-openapi-3-0-3/refractor-plugins/reference-summary.ts
Outdated
Show resolved
Hide resolved
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.
Two nitpicks related to naming, otherwise LGTM
f942461
to
9f14db7
Compare
@tekyu plese use Please also use commit message format described in: #3848 (comment) |
his plugin removes the
summary
anddescription
fields ofReference Object
.Refs SWG-10235
Refs #3697