Skip to content
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

Parsing json response funcion is now customizable (still defaults to … #1

Merged
merged 5 commits into from
Sep 3, 2018

Conversation

tdivis
Copy link
Contributor

@tdivis tdivis commented Sep 3, 2018

json.loads).

This allows to implement JSON-RPC class hinting or any other conversions.

…`json.loads`).

This allows to implement JSON-RPC class hinting or any other conversions.
@coveralls
Copy link

coveralls commented Sep 3, 2018

Coverage Status

Coverage remained the same at 100.0% when pulling 0a61fdc on tdivis:custom-loads into 7eb278d on armills:master.

In the case where our users aren't specifying a manual json.loads
method, we'd rather omit that argument, so that aiohttp can use its
logic to determine the default json.loads method.
We're not going to commit to loads being in a particular position in the
argument order on our API.
Copy link
Owner

@emlove emlove left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! I pushed up some small preference changes, mostly so that if loads isn't specified, we omit the argument to aiohttp entirely, so that it can continue to use it's current default determination.

@emlove emlove merged commit be718bb into emlove:master Sep 3, 2018
@tdivis
Copy link
Contributor Author

tdivis commented Sep 6, 2018

Great, good point, thanks :-).

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.

3 participants