Opened 15 years ago
Closed 15 years ago
#13457 closed (wontfix)
The Model Field Reference Shouldn't Use Alphabetical Order for the Fields
Reported by: | Mike Lissner | Owned by: | nobody |
---|---|---|---|
Component: | Documentation | Version: | 1.1 |
Severity: | Keywords: | ||
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
It would be much more useful if the field reference were done by type of field. This is done to some extent already, but it would help if simpler concepts were first, and more difficult ones were last, and if similar fields, such as those that store numbers and those that store text were sorted together.
Change History (2)
comment:1 by , 15 years ago
comment:2 by , 15 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
I agree with Gabriel. I don't see what we gain by having anything other than an alphabetical guide in the reference docs.
Note:
See TracTickets
for help on using tickets.
If it were in the "topics" or "intro" section of the docs I might agree, but it's "reference", and in my opinion reference materials should be sorted alphabetically for ease of ongoing lookup even at the cost of some confusion for new folks. To give an extreme example: where would the dictionary be if it were sorted by difficulty of the words?