-
Notifications
You must be signed in to change notification settings - Fork 83
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
Image->render() signature #146
Comments
Well as it's not really meant to use that parameter, I think we should patch |
atm |
xfra35
added a commit
that referenced
this issue
Jul 28, 2016
Ok thanks guys. Fixed then. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On the docs, we have the following signature:
But in reality, the
render()
method takes the same signature as imagejpeg and imagepng, which means the second argument should either beNULL
or a string or a stream.So what do you think guys? Should we fix the docs or fix
render()
?Fixing the docs is easy but on another hand, that extra second argument is useless as it should always be set to
NULL
sincerender()
is meant for output rendering.The same reflexion applies to
dump()
.The text was updated successfully, but these errors were encountered: