Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixed #16117 -- Added decorators for admin action and display functions. #13532
Fixed #16117 -- Added decorators for admin action and display functions. #13532
Changes from all commits
e8e402e
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So if I come to this documentation (or for
@display
) for the first time, it tells me about setting these attributes but not what they mean, and nor is there an obvious link to where to read about them. It makes it a bit hard to use@action
or@display
- it still feels like I have to know about both ways.Perhaps the decorator reference should become the canonical place where the meanings of the arguments and attributes are documented? At least, they can be briefly described with links to "more info" sections below, with each of the examples. The current structure is a fairly messy since it seems to have grown organically.
For actions:
short_description
is under "Writing action functions" onlyallowed_permissions
has a whole section "Setting permissions for actions"For display, everything is listed in bullet points under the
ModelAdmin.list_display
documentation (a giant list that starts "A few special cases"):boolean
- this unnecessarily re-spells what kinds of strings and functions are allowed inlist_display
admin_order_field
short_description
- this only has one sentence saying "As some examples have already demonstrated" which doesn't feel very easy to use as a reference since it's saying "go read above"empty_value_display
- this goes off on a bit of a tangent documenting the ability to change it for the whole admin site and the model admin class too. It would probably be best as its own section that documentation for the other two classes link to.I am suggesting a fair amount of docs rearrangement here. I am happy to shunt it to a second PR and help on that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree. It is quite impenetrable and definitely needs rejigging. I tried not to move stuff around too much at this stage, however, and kept everything in the same place.
I think a follow up PR to improve the whole of this section would be a good idea - the large bulleted list doesn't feel the best way to present the options.