New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for url namespaces #3563
Comments
allauth was conceived at around the same time Django namespaces were introduced, so historically it started out without namespaces. Currently, all url names still use prefixes, such as If your proposal is to take a first stab at making reversal namespace aware without breaking backwards compatiblity, then definitely, that is in any case a good thing to have. If you are referring to breaking backwards compatibility, then I would like to see more opinions on the matter first, and perhaps an investigation in how to ease the transition (e.g. |
@pennersr can i attempt this? |
As mentioned above, this is a big backwards compatibility issue, would like to get some opinions from other users on the matter first, as well as a decent proposal on how to move forward. |
Understood @pennersr . On the side note, i was wondering if it's possible to write you one email. I tired looking it up but couldn't find any. |
I was trying to include the allauth urls in a namespace as in:
The named urls are now all behind the namespace "v1" and cannot be reversed using the url name alone as in
reverse(url_name)
. Currently the django.url.reverse() function is used throughout the project with named urls without any consideration for url namespaces.The solution is to use something like:
What do you think about this issue, and do you think it is a good idea to work on it?
https://docs.djangoproject.com/en/5.0/topics/http/urls/#url-namespaces
The text was updated successfully, but these errors were encountered: