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

Optimize parse function: get json data from request directly #275

Merged
merged 3 commits into from
May 4, 2019

Conversation

strongbugman
Copy link
Contributor

@strongbugman strongbugman commented Jan 7, 2019

Resolves #274 #287

@pep8speaks
Copy link

pep8speaks commented Jan 7, 2019

Hello @strongbugman! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

There are currently no PEP 8 issues detected in this Pull Request. Cheers! 🍻

Comment last updated at 2019-03-08 07:56:57 UTC

@coveralls
Copy link

coveralls commented Jan 7, 2019

Coverage Status

Coverage decreased (-0.02%) to 91.162% when pulling e43cfc0 on strongbugman:feature/optimize_parser into 37ee864 on rochacbruno:master.

@strongbugman
Copy link
Contributor Author

Coverage Status

Coverage decreased (-0.02%) to 91.162% when pulling e43cfc0 on strongbugman:feature/optimize_parser into 37ee864 on rochacbruno:master.

I delete a little code so the coverage is reduced, actually, the code I contributed is all tested, so what should I do now?

@strongbugman
Copy link
Contributor Author

Broken by apispec.ext.marshmallow.openapi compatibility

@rochacbruno rochacbruno merged commit f82991a into flasgger:master May 4, 2019
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.

Array type not allowed in JSON body POST
4 participants