Opened 5 years ago
Closed 5 years ago
#31541 closed Cleanup/optimization (fixed)
Improve documentation of django.contrib.redirects.
Description (last modified by ) ¶
I think there are a couple small improvements that could be made to the docs here:
- The "Via the Python API" section could do with a simple shell example for creating a
Redirect
, since otherwise the fields aren't mentioned in the docs. I also imagine it might be used by relatively new users who aren't confident with the ORM. - The
Redirect.new_path
field'shelp_text
statesfull URL starting with “http://””
. This doesn't mention the now-more-commonhttps://
, nor the fact that arbitrary protocols are technically supported, such asonion://
. Perhapsfull URL starting with a scheme such as
https://
Change History (11)
comment:2 by , 5 years ago
Description: | modified (diff) |
---|---|
Summary: | Improve documentation of django.contrib.redirects → Improve documentation of django.contrib.redirects. |
Triage Stage: | Unreviewed → Accepted |
comment:3 by , 5 years ago
@mark no I didn't. But also this came from a Twitter conversation and the Djangonaut there was also interested in making a PR: https://twitter.com/Wildvasa/status/1257931805988134922 :)
comment:4 by , 5 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:6 by , 5 years ago
Patch needs improvement: | set |
---|
comment:7 by , 5 years ago
Patch needs improvement: | unset |
---|---|
Triage Stage: | Accepted → Ready for checkin |
comment:11 by , 5 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
I'd be happy to try to improve some of these docs unless you wanted to do that @adam