Skip to content

fix(twilio-run): correctly serialize JSON Responses #277

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 2 commits into from
Jun 17, 2021
Merged

Conversation

philnash
Copy link
Contributor

@philnash philnash commented Jun 8, 2021

Fixes #276

Contributing to Twilio

All third-party contributors acknowledge that any contributions they provide will be made under the same open-source license that the open-source project is provided under.

  • I acknowledge that all my contributions will be made under the project's license.

@philnash philnash requested a review from dkundel June 8, 2021 02:10
@philnash
Copy link
Contributor Author

philnash commented Jun 9, 2021

@dkundel This probably needs porting into the runtime-handler too.

@dkundel
Copy link
Contributor

dkundel commented Jun 9, 2021

Yes can we merge the runtime-handler first and then push this change? It's just easier to keep track of it that way.

@philnash
Copy link
Contributor Author

@dkundel Fixed this in runtime-handler too.

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.

Response objects with content type JSON are not returned correctly
2 participants