Fix router compatibility with DRF 3.8 #214
Merged
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.
Hi all. I authored encode/django-rest-framework#5705, which seems to have broken compatibility with the routers in drf-extensions. Fixing this seem seem to largely be just removing old code. Resolves #211
Changes:
ExtendedActionLinkRouterMixin
. This feature seems to have been originally developed around theget_dynamic_route_viewset_method_name_by_endpoint
method, but it's no longer called. Removing the class seems to have no effects on the tests (except for a few minor changes, see commit notes).get_regex_pattern
to handle regex pattern compatibility. This was added in DRF 3.7.4I've ran the tests locally, and the unit and functional router tests are passing. I haven't made an attempt to fix the remaining tests, as it's outside the scope of the PR.