Skip to content
GitLab

[php] Fix JSON object deserialization

Merged Administrator requested to merge github/fork/ybelenko/8394_json_decode_missing into master

Created by: ybelenko

When I call API via generated PHP client I got encoded json string instead of decoded object. Response looks like:

["{\"foobar\":\"foobaz\"}"]

UPD: I've checked response HTTP headers and Content-Type: application/json has been set correctly.

Closes #8394 (closed)

Circle-CI fail log:

09:30:50.626 [qtp2074407503-11] INFO  i.s.sample.resource.PetStoreResource - placeOrder ID 0 STATUS placed
09:30:50.628 [qtp2074407503-14] INFO  i.s.sample.resource.UserResource - createUser ID 1000 STATUS gopher
09:30:50.630 [qtp2074407503-14] INFO  i.s.sample.resource.UserResource - createUsersWithArrayInput
09:30:50.636 [qtp2074407503-14] INFO  i.s.sample.resource.UserResource - updateUser ID 1000 STATUS gopher
09:31:13.284 [qtp2074407503-22] INFO  i.s.sample.resource.PetResource - addPet ID 1611135073268 STATUS available

Too long with no output (exceeded 10m0s): context deadline exceeded

PR checklist

  • Read the contribution guidelines.
  • Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community.
  • Run the following to build the project and update samples: 
    ./mvnw clean package 
./bin/generate-samples.sh
./bin/utils/export_docs_generators.sh
    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*. For Windows users, please run the script in Git BASH.
  • File the PR against the correct branch: master, 5.1.x, 6.0.x
  • If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.

@jebentier, @dkarlovi, @mandrean, @jfastnacht, @ackintosh, @renepardon