#7284 closed (fixed)
foreign_key__related_fieldname documentation could be clearer
Reported by: | Owned by: | Simon Meers | |
---|---|---|---|
Component: | Documentation | Version: | dev |
Severity: | Keywords: | foreign_key | |
Cc: | Triage Stage: | Ready for checkin | |
Has patch: | yes | 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 (last modified by ) ¶
Documentation could be clearer in this area. The existing example
search_fields = ['foreign_key__related_fieldname']
is a bit confusing absent a real table and example of the sort
search_fields = [user__name]
or some such would be helpful as it took me, and I suspect many others, a bit of effort to discover the desired syntax.
Change History (9)
comment:1 by , 17 years ago
Description: | modified (diff) |
---|
comment:2 by , 17 years ago
Triage Stage: | Unreviewed → Accepted |
---|
by , 15 years ago
comment:3 by , 15 years ago
Has patch: | set |
---|
comment:4 by , 15 years ago
milestone: | → 1.3 |
---|---|
Owner: | changed from | to
Status: | new → assigned |
Triage Stage: | Accepted → Ready for checkin |
comment:5 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
comment:6 by , 15 years ago
Note:
See TracTickets
for help on using tickets.
Clarifying example added as requested.