-
-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
Remove browser overriding #3410
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Update transifex-client requirement to latest release version 0.11b3
…nassa/django-rest-framework into canassa-method-not-allowed-not-raised
edmorley
pushed a commit
to mozilla/treeherder
that referenced
this pull request
Nov 13, 2015
The default format used to make test requests is `multipart/form-data`, unless overridden using `TEST_REQUEST_DEFAULT_FORMAT`: http://www.django-rest-framework.org/api-guide/testing/#setting-the-default-format Our API only accepts json and html (see `DEFAULT_RENDERER_CLASSES`), so we should have always been setting `TEST_REQUEST_DEFAULT_FORMAT` to `json`, to prevent test failures. However until recently there was a bug preventing those failures: encode/django-rest-framework#3214 Which has now been fixed in django-rest-framwork v3.3.x: encode/django-rest-framework#3410 ...so we must fix this before updating to the latest version of d-r-f.
edmorley
pushed a commit
to mozilla/treeherder
that referenced
this pull request
Dec 6, 2015
The default format used to make test requests is `multipart/form-data`, unless overridden using `TEST_REQUEST_DEFAULT_FORMAT`: http://www.django-rest-framework.org/api-guide/testing/#setting-the-default-format Our API only accepts json and html (see `DEFAULT_RENDERER_CLASSES`), so we should have always been setting `TEST_REQUEST_DEFAULT_FORMAT` to `json`, to prevent test failures. However until recently there was a bug preventing those failures: encode/django-rest-framework#3214 Which has now been fixed in django-rest-framwork v3.3.x: encode/django-rest-framework#3410 ...so we must fix this before updating to the latest version of d-r-f.
edmorley
pushed a commit
to mozilla/treeherder
that referenced
this pull request
Dec 10, 2015
…pe json The default format used to make test requests is `multipart/form-data`, unless overridden using `TEST_REQUEST_DEFAULT_FORMAT`: http://www.django-rest-framework.org/api-guide/testing/#setting-the-default-format Our API only accepts json and html (see `DEFAULT_RENDERER_CLASSES`), so we should have always been setting `TEST_REQUEST_DEFAULT_FORMAT` to `json`, to prevent test failures. However until recently there was a bug preventing those failures: encode/django-rest-framework#3214 Which has now been fixed in django-rest-framwork v3.3.x: encode/django-rest-framework#3410 ...so we must fix this before updating to the latest version of d-r-f.
This was referenced Mar 9, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Method and Content-Type overriding supported via AJAX in the browsable API, rather than dealt with server-side.
Still to do:
Closes #1769.
Refs #1174, #1346.