#21938 closed Cleanup/optimization (fixed)
Improve docs/ref/views.txt
| Reported by: | Tim Graham | Owned by: | JLinden |
|---|---|---|---|
| Component: | Documentation | Version: | 1.6 |
| Severity: | Normal | Keywords: | afraid-to-commit |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | yes | UI/UX: | no |
Description
As noted in this PR, the "Built-in views" page isn't very useful. We should expand this page into a proper reference guide for the functions in django.views, probably moving some content from topics/http/views.txt.
Change History (8)
comment:1 by , 11 years ago
comment:2 by , 11 years ago
| Keywords: | afraid-to-commit added |
|---|
Ear-marked as suitable for a first-time committer at DjangoCon Europe 2014.
comment:3 by , 11 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:4 by , 11 years ago
The error views are currently ordered by most commonly used, should we keep it that way or order them by status code instead? As in 400, 403, 404, 500.
comment:5 by , 11 years ago
I think the current order is okay, but I don't feel strongly about it. We are likely to replace them with something more generic anyway (see #22058).
comment:6 by , 11 years ago
Ok, the order stays as it is.
I've sent a PR with my changes at https://github.com/django/django/pull/2710
Version 0, edited 11 years ago by (next)
comment:7 by , 11 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
I totally Agree to your point. For new users view's functions need to be defined more practically for usage. I'm a newbie here, but I'd like to contribute to this fix. I'd be glad to help out and write the documentation part.