-
Notifications
You must be signed in to change notification settings - Fork 6k
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
fix(go): return decoding errors #10429
Merged
Merged
Conversation
This file contains 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
kevinawoo
added a commit
to armory/spin
that referenced
this pull request
Aug 17, 2020
…parsing errors swagger-api/swagger-codegen#10429 will add that ability back in.
kevinawoo
added a commit
to armory/spin
that referenced
this pull request
Aug 18, 2020
This also removes "*malformed" test cases since 2.14.4 doesn't return parsing errors swagger-api/swagger-codegen#10434 reports the issue. hopefully swagger-api/swagger-codegen#10429 be merged will add that ability back in.
mergify bot
pushed a commit
to spinnaker/spin
that referenced
this pull request
Aug 18, 2020
* chore(gateapi): update gateapi from 5c625da5 using swagger 2.4.14 * feat(contribution): add instructions on how to generate gateapi using 2.4.1 * refact(gateapi): swagger 2.4.14 query params are typed now * tests(gateapi): gateapi generated code expects valid JSON and headers This also removes "*malformed" test cases since 2.14.4 doesn't return parsing errors swagger-api/swagger-codegen#10434 reports the issue. hopefully swagger-api/swagger-codegen#10429 be merged will add that ability back in. * refactor(imports): fixed import styling * chore(gateapi): use swagger-cli 2.4.15
gsapkal
pushed a commit
to gsapkal/spin
that referenced
this pull request
Sep 10, 2020
…#292) * chore(gateapi): update gateapi from 5c625da5 using swagger 2.4.14 * feat(contribution): add instructions on how to generate gateapi using 2.4.1 * refact(gateapi): swagger 2.4.14 query params are typed now * tests(gateapi): gateapi generated code expects valid JSON and headers This also removes "*malformed" test cases since 2.14.4 doesn't return parsing errors swagger-api/swagger-codegen#10434 reports the issue. hopefully swagger-api/swagger-codegen#10429 be merged will add that ability back in. * refactor(imports): fixed import styling * chore(gateapi): use swagger-cli 2.4.15
thanks @kevinawoo !! |
This was referenced Mar 11, 2021
This was referenced Mar 11, 2021
Open
Merged
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.
PR checklist
./bin/
to update Petstore sample so that CIs can verify the change. (For instance, only need to run./bin/{LANG}-petstore.sh
and./bin/security/{LANG}-petstore.sh
if updating the {LANG} (e.g. php, ruby, python, etc) code generator or {LANG} client's mustache templates). Windows batch files can be found in.\bin\windows\
.3.0.0
branch for changes related to OpenAPI spec 3.0. Default:master
.Description of the PR
We're not returning a
a.client.decode
ing error which is helpful for callers to determine what's wrong with an API call.