-
Notifications
You must be signed in to change notification settings - Fork 279
Add filterByOperationId command option #636
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
Conversation
…ed on OperationId
| var stream = GetStream(input); | ||
|
|
||
| OpenApiDocument document; | ||
|
|
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.
Defensive programming for the params?
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.
The version and format params have default values, so they can't equate to null at any point.
operationIds is nullable since its an optional filtering parameter.
…o mk/add-filter-commandOption
This PR proposes adding a filterByOperationId parameter to the Commandline tool by:
--filterByOperationIdcommand option to thetransformcommandOpenApiFilterServicethat slices an OpenApiDocument based on theoperation IdsprovidedTesting Instructions
.\build.cmdfileopenapi-parsertool locally by running the.\install-tool.ps1script.\artifacts\openapi-parser.exefile and call the transform command--filterByOperationId "operationId"parameter to the transform commandE.g:
.\artifacts\openapi-parser.exe transform --input People.yml --format yaml --output People2.yml --version OpenApi3_0 --filterByOperationId users_UpdateInsightsFixes #631