Force DRF Docs to provide Headers input #638
Merged
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
ian-ross
force-pushed
the
enhancement/drf-docs-authentication
branch
from
e17724d to
4f3c296
Compare
|
Seems to work for basic stuff, but I'm getting an authentication error for anything that requires a token:
|
ian-ross
force-pushed
the
enhancement/drf-docs-authentication
branch
from
4f3c296 to
d82fa55
Compare
This is needed to be able to provide an authentication token to drive the API endpoints from the HTML API views.
|
@linzjax It works for me, I think, you forgot to add |
oliverroick
force-pushed
the
enhancement/drf-docs-authentication
branch
from
d82fa55 to
9de5ae1
Compare
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.
Proposed changes in this pull request
The live API endpoints provided by the DRF Docs tool that live at
/api/v1/docsneed to provide a way of setting up HTTP headers to provide an authentication token (by setting anAuthorizationheader to sayToken <token-value>). This is because of some default settings in the DRF Docs setup. This PR changes those settings to force DRF Docs to provide a way of setting headers for all the live API endpoints.When should this PR be merged
I believe that this can be merged at any time, but I'd like for @linzjax and @oliverroick to take a look at it first.
Risks
Low to none.
Follow up actions
None.