raise ImproperlyConfigured exception if basename is not unique
#8438
Conversation
This file contains hidden or 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
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
@sevdog can you review this please? |
auvipy
requested changes
Nov 22, 2022
sevdog
suggested changes
Nov 22, 2022
dgravitate
force-pushed
the
reject-duplicate-basenames
branch
from
7081209 to
badd1c1
Compare
auvipy
requested changes
Dec 1, 2022
Added additional tests using DefaultRouter |
auvipy
approved these changes
Dec 8, 2022
|
I think this should be accepted as this change add checks which is good for developer experience. And not introduce any API surface or major behavioral changes |
auvipy
requested changes
Dec 10, 2022
auvipy
approved these changes
Dec 10, 2022
kernicPanel
added a commit
to openfun/joanie
that referenced
this pull request
Mar 18, 2024
DRF verson 3.15 raises a ImproperlyConfigured exception if url basenames are not uniques. encode/django-rest-framework#8438
kernicPanel
added a commit
to openfun/joanie
that referenced
this pull request
Mar 18, 2024
DRF verson 3.15 raises a ImproperlyConfigured exception if url basenames are not uniques. encode/django-rest-framework#8438
This was referenced Mar 23, 2024
tijuca
added a commit
to tijuca/drf-extensions
that referenced
this pull request
Mar 24, 2024
Since DRF 3.15.0 a unique basename must be used due encode/django-rest-framework#8438 Fixes chibisov#341
2 tasks
auvipy
added a commit
to chibisov/drf-extensions
that referenced
this pull request
Sep 4, 2024
* tests: Use basename='xxx' to set a unique basename Since DRF 3.15.0 a unique basename must be used due encode/django-rest-framework#8438 Fixes #341 * Update tests_app/tests/functional/mixins/detail_serializer_mixin/urls.py --------- Co-authored-by: Asif Saif Uddin <[email protected]>
m-haines
added a commit
to cedadev/app_datamad
that referenced
this pull request
Oct 7, 2024
…mysqlclient. This resulted in the following changes having to be made
# Django 3.2 -> 4.2 changes
## ./datamad2/models/users.py
from django.utils.translation import ugettext_lazy as _ --> from django.utils.translation import gettext_lazy as _
## ./datamad2/admin.py
admin.site.register(User, UserAdmin) etc at eof changed to @admin.register(User) decorator above class definition of the user type. eof registers all deleted
Slightly concerned this does not give the same functionality, TODO check
## ./datamad2/utils.py
from django.utils.encoding import force_text --> from django.utils.encoding import force_str
## ./datamadsite/settings.py
USE_L10N = True --> line deleted
crispy_bootstrap4 added to INSTALLED_APPS
# ./datamadsite/settings_local.py.tmpl
Added the Additional allowed template packs:
CRISPY_ALLOWED_TEMPLATE_PACKS = "bootstrap4"
CRISPY_TEMPLATE_PACK = "bootstrap4"
# bootstrap_datepicker_plus updates
## grants.py and data_products.py
from bootstrap_datepicker_plus import DatePickerInput --> from bootstrap_datepicker_plus.widgets import DatePickerInput
## Changed format='' for bootstrap_datepicker_plus.widgets.DatePickerInput from format='%d/%m/%Y' to options={'format':'%d/%m/%Y'} to fix the following error:
./app_datamad_new/Lib/site-packages/bootstrap_datepicker_plus/_base.py:38:
FutureWarning: The 'format' parameter is ignored, set 'format' in options instead.
see https://github.com/monim67/django-bootstrap-datepicker-plusbootstrap_datepicker_plus.widgets
Removed ifequal from pagination.html as it was removed in Django 4.0 and replaced with "if x = condition" instead
# djangorestframework updating to 3.15.2 from 3.12.4
# Updating to drf 3.15.2 from 3.12.4, had to specify basename for datacentres/ datacenter in datamad2_api/urls.py due to importing name from "DataCentre" model queryset leading to identical routings for the "datacentre" and "datacenter" base URLs.
This is due to a change from drf 3.14 -> 3.15 enforcing the following encode/django-rest-framework#8438
Added new script DataMad_csv_create.py to import data from UKRIs DataBank database into a .csv file
Created two example Docker files for local debugging, if the user wanted to.
setup.py to Python 3.12 from Python 3.6
Updated the README.md file.
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.
When
basenameis dynamically generated inBaseRouter.get_default_basename, it could (and does) generate a conflicting basename when multiple routes use the same Model. Additionally, developers could inadvertently use a basename that has already been used elsewhere.In either case, this can lead to unexpected results when (correctly) using
reverse()to get the URL