#35090: Enforce uniqueness on custom path converters
-------------------------------------+-------------------------------------
Reporter: Adam Johnson | Owner: Salvo
Type: | Polizzi
Cleanup/optimization | Status: assigned
Component: Core (URLs) | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 1
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Salvo Polizzi):
Replying to [comment:8 Natalia Bidart]:
> I'm not sure I understand the desired fix: is it to prevent any
converter registered name overlap (ie a dynamic check at the time of
project load)? or just a check against the Django/default's converters?
I interpreted it as an issue to avoid overlapping among different
registered converters, but please correct me if I misunderstood.
> Would there be a way to override registered converters?
I honestly don't know if there is a possibility to override
--
Ticket URL: <https://code.djangoproject.com/ticket/35090#comment:11>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018cfd2640b0-996ab93e-a9fb-4470-99ce-17f61b8e7480-000000%40eu-central-1.amazonses.com.
