We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi,
Using Panko::Response.new, we are not able to render a hash in the response as we get an error thrown Can not push onto an Object without a key..
Panko::Response.new
Can not push onto an Object without a key.
For example, doing it with normal render json works as follows:
my_hash = { foo: 'bar', bar: 'foo' } render json: { my_hash: my_hash }
This will give a response looking like: {"my_hash":{"foo":"bar","bar":"foo"}}.
{"my_hash":{"foo":"bar","bar":"foo"}}
However using Panko::Response, the error is thrown:
my_hash = { foo: 'bar', bar: 'foo' } render json: Panko::Response.new( my_hash: my_hash )
Will give error: Can not push onto an Object without a key..
Please let me know if any additional info is required.
Thanks for this awesome gem! Laith
The text was updated successfully, but these errors were encountered:
Hi @LaithAzer ,
Thanks!
I will look into it today.
Sorry, something went wrong.
Panko::Response - fix hash support #32
e2ae8b1
Fixed the issue in the commit above, will release a version today/tomorrow.
Sorry for wait time
@LaithAzer version 0.5.6 is released to address this issue
No branches or pull requests
Hi,
Using
Panko::Response.new
, we are not able to render a hash in the response as we get an error thrownCan not push onto an Object without a key.
.For example, doing it with normal render json works as follows:
This will give a response looking like:
{"my_hash":{"foo":"bar","bar":"foo"}}
.However using Panko::Response, the error is thrown:
Will give error:
Can not push onto an Object without a key.
.Please let me know if any additional info is required.
Thanks for this awesome gem!
Laith
The text was updated successfully, but these errors were encountered: