Skip to content

Fix response object marshalling - #618

Merged
TheSmartnik merged 1 commit into
masterfrom
allow_marshalling_response_object
Nov 10, 2018
Merged

Fix response object marshalling#618
TheSmartnik merged 1 commit into
masterfrom
allow_marshalling_response_object

Conversation

@TheSmartnik

Copy link
Copy Markdown
Collaborator

Fixes #143

@jnunemaker Hi, would love to hear your feedback on this one. It looks fine, but I could've forget something

@TheSmartnik
TheSmartnik merged commit 019458d into master Nov 10, 2018
@TheSmartnik
TheSmartnik deleted the allow_marshalling_response_object branch November 10, 2018 14:48
baberthal added a commit to baberthal/httparty that referenced this pull request Oct 31, 2020
This PR fixes the issue(s) described in jnunemaker#713. To fix the logger option
issue, I simply delete `Request.options[:logger]` when dumping. To fix
the proc parser issue, I delete `Request.options[:parser]` if and only
if `Request.options[:logger]` is a proc. If `Request.options[:logger]`
is a regular class, `Marshal.dump` should proceed as normal. This should
not affect the `Marshal.dump` behavior described in issue jnunemaker#143 and fixed
by PR jnunemaker#618.

I have added a feature spec to make sure marshalling the request
works as intended, as well as a unit test to ensure
`Marshal.load(Marshal.dump(req))` works as it should.
@baberthal baberthal mentioned this pull request Oct 31, 2020
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.

1 participant