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

Fixes related to #142 #161

Merged
merged 7 commits into from
Jul 14, 2021
Merged

Fixes related to #142 #161

merged 7 commits into from
Jul 14, 2021

Conversation

cuducos
Copy link
Contributor

@cuducos cuducos commented Jul 13, 2021

Given the question raised in #160, these changes follow the option to keep the changes in the code and update the tests to match this new state.


UPDATE as the CI was still red due to security issues with Django and aiohttp, I'm bringing in some updates suggested in #159.

@cuducos cuducos force-pushed the update-tests-after-pr-142 branch 5 times, most recently from 3110ca6 to 0576e92 Compare July 13, 2021 23:42
pyup-bot and others added 6 commits July 13, 2021 19:46
According to Django docs[1]:

> If it’s set to False, any object can be passed for serialization
> (otherwise only dict instances are allowed)

As we are using a dict, there's no need for the safe=False.

[1] https://docs.djangoproject.com/en/3.2/ref/request-response/#jsonresponse-objects
Aligns with changes from #142
@ogecece
Copy link
Member

ogecece commented Jul 14, 2021

LGTM! Thanks @cuducos !

I'm approving and merging this.

Though, it's important we clarify #160 to know if the changes in #142 were intended or not.

@ogecece ogecece merged commit 22ddd34 into main Jul 14, 2021
@ogecece ogecece deleted the update-tests-after-pr-142 branch July 14, 2021 22:34
@adorilson adorilson mentioned this pull request Jul 15, 2021
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.

None yet

3 participants