fix(schema): anyOf must contains an array, not an object #7399
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.
Fix invalid anyOf usage in schema generation
The schema currently defines anyOf as an object instead of an array, which is invalid. Spectral linting (docker run --rm -it -v $(pwd):/tmp stoplight/spectral:6 lint /tmp/openapi.yaml) reports:
"anyOf property must be array."
This PR wraps $schemas with array_values, ensuring anyOf receives an array. The same approach is already used in other parts of the code.