-
Notifications
You must be signed in to change notification settings - Fork 464
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
to_json causes and error #555
Comments
Hi @rhuberdeau Thanks for opening a new issue! Can you open a PR with the fix implemented? |
Hi @JenniferMah. I'd be happy to open a PR but I wasn't able to come up with a test that replicates the bug. From what I can tell this issue doesn't pop up until the gem is installed into a Rails app. |
In case someone is coming here to find a fix: I found this response by @eshanholtz really helpful: #524 (comment) You can use the following to get the raw http response:
|
@rhuberdeau Can you test this in latest version and see if this issue exists? I tried to reproduce this issue with the same steps mentioned above, but couldn't succeed. If the issue is still there, can you please provide the below information?
|
@AsabuHere I have the same problem with to_json/as_json methods.
Steps to reproduce (Twilio Video example):
Result: |
Issue Summary
Stack level too deep error when calling to_json on a response object
This is a duplicate of #423 which was closed due to "no activity"
Steps to Reproduce
@childish-sambino added a fix to the closed ticket which works for me if I add it to domain.rb
Code Snippet
Technical details:
The text was updated successfully, but these errors were encountered: