Code

Opened 4 years ago

Closed 4 years ago

#13457 closed (wontfix)

The Model Field Reference Shouldn't Use Alphabetical Order for the Fields

Reported by: mlissner 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: UI/UX:

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.

Attachments (0)

Change History (2)

comment:1 Changed 4 years ago by gabrielhurley

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset

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?

comment:2 Changed 4 years ago by russellm

  • Resolution set to wontfix
  • Status changed from new to closed

I agree with Gabriel. I don't see what we gain by having anything other than an alphabetical guide in the reference docs.

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.