[pavog]

With enumUnknownDefaultCase enabled, the php-nextgen generator adds an UNKNOWN_DEFAULT_OPEN_API case to every enum, but ObjectSerializer::deserialize() never used it. Deserializing a response with an unknown enum value still threw: InvalidArgumentException: Invalid value for enum \Example\Model\FileStatus’ must be one of: ...

This PR falls back to the unknown default case in ObjectSerializer::deserialize(), using the same check as the php generator. Serialization is unchanged, so unknown values are still rejected when sending requests.

The existing enumUnknownDefaultCase tests now also check the generated ObjectSerializer. The php-nextgen samples don't change, as none of them enables the option.
I also verified the fix with clients generated from real specs, for integer and string backed enums.

PR checklist

• Read the contribution guidelines.
• Run the following to build the project and update samples:

  ./mvnw clean package || exit
  ./bin/generate-samples.sh ./bin/configs/*.yaml || exit
  ./bin/utils/export_docs_generators.sh || exit
  

• If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.

PHP: @jebentier @dkarlovi @mandrean @jfastnacht @ybelenko @renepardon

---

Summary by cubic

Fixes php-nextgen deserialization so that unknown enum values fall back to the UNKNOWN_DEFAULT_OPEN_API case when enumUnknownDefaultCase is enabled, instead of throwing an InvalidArgumentException. Serialization is unchanged, and unknown values are still rejected when sending requests.

• Adds the fallback check in ObjectSerializer::deserialize(), matching the existing php generator behavior.
• Extends the enumUnknownDefaultCase tests to verify the generated ObjectSerializer code for both enabled and disabled states.

^{Written for commit 3cf8f57. Summary will update on new commits.}

[cubic-dev-ai]

No issues found across 2 files

_{View guided diff | Re-trigger cubic}