Repository navigation
[Server] Fix variadic enum parameters declaring their items as objects - #735
Open
skybleak333 wants to merge 1 commit into
Open
skybleak333 wants to merge 1 commit into
skybleak333 wants to merge 1 commit into
Conversation
skybleak333
requested review from
CodeWithKyrian,
Nyholm,
chr-hertel and
soyuka
as code owners
November 11, 2026 11:15
This branch has not been deployed
This file contains hidden or 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
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.
A variadic enum parameter like
Color ...$colorswas advertised as{"type": "array", "items": {"type": "object"}}, so{"colors": ["red", "blue"]}got-32602 Expected object, but received stringand no input could reach the handler. The items now list the enum's values, like for a single enum parameter, so the call validates and the handler gets the enum cases.Found, fixed and written up with Claude Code.