Handle reversal of non-API view_name in HyperLinkedRelatedField #2724
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
|
I wonder if we should handle this in a more generic way - eg in the reverse function... https://github.com/tomchristie/django-rest-framework/blob/master/rest_framework/reverse.py#L18 Wrap the |
|
Yeah, I think you are right. I'll try do do that. |
|
Moved the fallback logic to |
|
Excellent! |
|
Stupidly I managed to miss this for the 3.1.1 release - apologies. |
tomchristie
added a commit
that referenced
this pull request
Mar 23, 2015
…i-reversal Handle reversal of non-API view_name in HyperLinkedRelatedField
This was referenced Mar 9, 2017
This was referenced Oct 16, 2017
This was referenced Nov 6, 2017
This was referenced Nov 14, 2017
This was referenced Dec 10, 2017
This was referenced Dec 20, 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.
This fixes #2711