Opened 4 months ago
Last modified 4 months ago
#35824 assigned Cleanup/optimization
Improve patch_cache_control documentation
Reported by: | Adam Johnson | Owned by: | Waqas Younas |
---|---|---|---|
Component: | Documentation | Version: | dev |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Accepted | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Pull Requests: | How to create a pull request | ||
Description ¶
The documentation for this response modifier lists rules, but only rules. It would be a lot clearer with a table of transformed names for common parameters and a usage example.
According to the ticket's flags, the next step(s) to move this issue forward are:
- To provide a patch by sending a pull request. Claim the ticket when you start working so that someone else doesn't duplicate effort. Before sending a pull request, review your work against the patch review checklist. Check the "Has patch" flag on the ticket after sending a pull request and include a link to the pull request in the ticket comment when making that update. The usual format is:
[https://github.com/django/django/pull/#### PR]
.
Change History (2)
comment:1 by , 4 months ago
Triage Stage: | Unreviewed → Accepted |
---|
comment:2 by , 4 months ago
Owner: | set to |
---|---|
Status: | new → assigned |
Hello, I'm new to Django and I'd like to solve this so I've assigned this to myself as my first ticket :).
Next step for me: figure out where that change needs to be made in the docs.
Note:
See TracTickets
for help on using tickets.
Agreed - I think that would be a nice improvement