-
-
Notifications
You must be signed in to change notification settings - Fork 399
[Features] - response declarations, "default" status codes as success response types #17
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
Merged
js2me
merged 20 commits into
next
from
feature/response-variations-in-request-description
Feb 27, 2020
Merged
[Features] - response declarations, "default" status codes as success response types #17
js2me
merged 20 commits into
next
from
feature/response-variations-in-request-description
Feb 27, 2020
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…equest responses)
…ss response status code)
js2me
commented
Feb 26, 2020
jar3b
approved these changes
Feb 27, 2020
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.
ok
…ations-in-request-description
…chines via nodejs
…ations-in-request-description
…ations-in-request-description
…test): add manual test for new option; docs: update CHANGELOG + README
…ations-in-request-description
js2me
added a commit
that referenced
this pull request
Feb 28, 2020
* test(internal): speed improve validate generated ts api modules * BREAKING_CHANGE: default typescript api file name (api.ts -> Api.ts) * feat: improve response body type definitions * chore(docs): add gtihub funding * [Bugfix] Response type does not de-reference $refs (#19) * chore: add common test schemas * refactor: encapsulate nodejs.fs module usage; feat: dereference components responses + improve types * chore: add specific comments for calling src/index.js on unix like machines via nodejs * chore: update gitignore (add hidden test cli file) * fix: JSDOC comments * [Features] - response declarations, "default" status codes as success response types (#17) * feat: add @returns keywords into each request comments description (request responses) * feat: prettify descriptions * feat: add response declarations in request description; feat: typed bad responses * feat: -d, --default-as-success option (ability to use "default" success response status code) * chore: add common test schemas * fix: description of defaultResponseAsSuccess option * chore: rename setConfig to addToConfig * chore: add specific comments for calling src/index.js on unix like machines via nodejs * feat: move responses declarations into flag '-r, --responses'; chore(test): add manual test for new option; docs: update CHANGELOG + README * fix: format description (end \n character) * bump: up version to 1.4.0
js2me
added a commit
that referenced
this pull request
Mar 2, 2020
* test(internal): speed improve validate generated ts api modules * BREAKING_CHANGE: default typescript api file name (api.ts -> Api.ts) * feat: improve response body type definitions * chore(docs): add gtihub funding * [Bugfix] Response type does not de-reference $refs (#19) * chore: add common test schemas * refactor: encapsulate nodejs.fs module usage; feat: dereference components responses + improve types * chore: add specific comments for calling src/index.js on unix like machines via nodejs * chore: update gitignore (add hidden test cli file) * fix: JSDOC comments * [Features] - response declarations, "default" status codes as success response types (#17) * feat: add @returns keywords into each request comments description (request responses) * feat: prettify descriptions * feat: add response declarations in request description; feat: typed bad responses * feat: -d, --default-as-success option (ability to use "default" success response status code) * chore: add common test schemas * fix: description of defaultResponseAsSuccess option * chore: rename setConfig to addToConfig * chore: add specific comments for calling src/index.js on unix like machines via nodejs * feat: move responses declarations into flag '-r, --responses'; chore(test): add manual test for new option; docs: update CHANGELOG + README * fix: format description (end \n character) * bump: up version to 1.4.0 * chore(docs): update CHANGELOG after release * [Internal] prettier with hooks (#21) * feat: add prettier with husky hooks * fix: prettierrc * chore: prettier ignore test generated apis * [Bugfix] TypeScript 3.7.5 error in the strict mode inside addQueryParams method * chore: refresh generated test api modules * bump: up version to 1.4.1; docs: update CHANGELOG; Co-authored-by: Henadz Yermakavets <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
-d, --default-as-success
option. Allows to use "default" status codes as success response type