-
Notifications
You must be signed in to change notification settings - Fork 50
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
Clean-up URLs #29
Comments
Merged
Wouldn't following this be able to help with the redirecting apsect? https://stackoverflow.com/questions/14959217/django-url-redirect |
1.0 should just drop the "old" URLs (that don't have trailing slashes). |
Oh yes please! |
akx
added a commit
that referenced
this issue
Jul 4, 2022
* URLs require the trailing slash, as is the Django (and allauth) way * URLs no longer have a hard-coded "two-factor/" prefix; like with allauth, the prefix is left for the `include()`r to decide * URLs have dashes instead of underscores (like allauth) Fixes #29
Merged
akx
added a commit
that referenced
this issue
Jul 4, 2022
* URLs require the trailing slash, as is the Django (and allauth) way * URLs no longer have a hard-coded "two-factor/" prefix; like with allauth, the prefix is left for the `include()`r to decide * URLs have dashes instead of underscores (like allauth) Fixes #29
akx
added a commit
that referenced
this issue
Jul 7, 2022
* URLs require the trailing slash, as is the Django (and allauth) way * URLs no longer have a hard-coded "two-factor/" prefix; like with allauth, the prefix is left for the `include()`r to decide * URLs have dashes instead of underscores (like allauth) Fixes #29
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The URLs we include are kind of a mess:
Theoretically we can just change these if people use names, but we would probably want to include redirects. It could also be nice to use a namespace.
The text was updated successfully, but these errors were encountered: