Skip to content

Fix content-type POST conditions #83

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 1 commit into from
Mar 12, 2018
Merged

Fix content-type POST conditions #83

merged 1 commit into from
Mar 12, 2018

Conversation

codingjoe
Copy link
Owner

POST conditions seem to be exclusive, so all conditions have to
match not only one of them. Therefore we need to remove the
condition if multiple content types are expected.

POST conditions seem to be exclusive, so all conditions have to
match not only one of them. Therefore we need to remove the
condition if multiple content types are expected.
@codecov
Copy link

codecov bot commented Mar 12, 2018

Codecov Report

Merging #83 into master will not change coverage.
The diff coverage is 100%.

Impacted file tree graph

@@          Coverage Diff          @@
##           master    #83   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files           4      4           
  Lines          73     70    -3     
=====================================
- Hits           73     70    -3
Impacted Files Coverage Δ
s3file/forms.py 100% <100%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5b978c1...03fa62b. Read the comment docs.

@codingjoe codingjoe merged commit b270658 into master Mar 12, 2018
@codingjoe codingjoe deleted the fix/conditions branch March 12, 2018 13:27
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

1 participant