Skip to content

fix bug: "Argument of type NULL should have been an array" when argument is optional #30

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 18, 2016

Conversation

kranikitao
Copy link
Contributor

No description provided.

@matthiasnoback
Copy link
Owner

Hi! Thanks for your work on this. Could you show me an example of the service definition that would result in null being used for an optional array-type argument? I thought that an array-type parameter would never be satisfied by null (only if the argument is left out).

@matthiasnoback
Copy link
Owner

Okay, it turns out this is possible - I learned something new today about PHP :) See also https://3v4l.org/rW2B5

matthiasnoback added a commit that referenced this pull request Feb 18, 2016
fix bug: "Argument of type NULL should have been an array" when argument is optional
@matthiasnoback matthiasnoback merged commit 6535548 into matthiasnoback:master Feb 18, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants