[PHP] - Add range HTTP code support #20992
Merged
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.
Adds ranged HTTP code support to the php and php-nextgen generators.
Given:
we want the API endpoint to handle a range of HTTP codes between
400
and499
.Additional fixes:
The php/psr-18 currently generates broken code:
Additional refactoring:
Creates new method inside Api classes,
::handleResponseWithDataType()
. This method handles the repeated code throughout the Api classes that check response code against a list and returns the deserialized object type.Finally, there appears to be a bug in how non-2xx HTTP codes are handled. Given a set of response codes 200 and 400:
the generated code before this PR looks like this:
The line
if ($statusCode < 200 || $statusCode > 299) {
never gets triggered to throw an exception because theswitch
finds a match incase 400:
.This may not matter because my understanding is the
$response = $this->client->send($request, $options);
call will throw an exception on any non-2xx response code, triggering the followingcatch
:PR checklist
Commit all changed files.
This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
These must match the expectations made by your contribution.
You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example
./bin/generate-samples.sh bin/configs/java*
.IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed.
master
(upcoming7.x.0
minor release - breaking changes with fallbacks),8.0.x
(breaking changes without fallbacks)