Repository navigation
[Server] Fix iterable parameters being declared as objects - #736
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:16
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.
An
iterable $itemsparameter was advertised as{"type": "object"}, so{"items": [1, 2]}got-32602 Expected object, but received array, althoughiterable<T>already maps toarrayand the argument is cast like anarrayone. It now gets{"type": "array"}, which means a JSON object is refused instead, as forarray, hence the[BC Break]entry.Found, fixed and written up with Claude Code.