-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Data views: Make trash a quick action again #60165
Conversation
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Size Change: +52 B (0%) Total Size: 1.72 MB
ℹ️ View Unchanged
|
While you're at it, can you also fix this incorrect i18n code?
For the second |
Let me know if I got that one right! |
It should be more like:
|
It's not quite coming together for me with this:
Feel free to push directly to this branch if you prefer. |
@jasmussen You're missing the third parameter to Consult the readme for how |
Co-authored-by: Pascal Birchler <pascalb@google.com>
Thanks, I've added this for now. It's giving me warnings in my editor, though: A quick ping to @jorgefilipecosta as well — I was not involved in the original pieces here, so I've not been as close to this part of the codebase. |
Simply forgot a comma, that's all. Like the error message says |
Co-authored-by: Pascal Birchler <pascalb@google.com>
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.
Let's get this in, thanks!
* Data views: Make trash a quick action again * Use _n * Update packages/edit-site/src/components/actions/index.js Co-authored-by: Pascal Birchler <pascalb@google.com> * Update packages/edit-site/src/components/actions/index.js Co-authored-by: Pascal Birchler <pascalb@google.com> --------- Co-authored-by: Pascal Birchler <pascalb@google.com> Co-authored-by: Jorge Costa <jorge.costa@developer.pt>
* Data views: Make trash a quick action again * Use _n * Update packages/edit-site/src/components/actions/index.js Co-authored-by: Pascal Birchler <pascalb@google.com> * Update packages/edit-site/src/components/actions/index.js Co-authored-by: Pascal Birchler <pascalb@google.com> --------- Co-authored-by: Pascal Birchler <pascalb@google.com> Co-authored-by: Jorge Costa <jorge.costa@developer.pt>
What?
Followup to #59551. I misunderstood some of the changes in the PR, as far as what type of destructive actions were moved to the ellipsis menu. This moves the "trash" button back as a quick action.
Why?
Deleting pages are only partially destructive actions, insofar as they move a page or post to a trashcan vs. erasing them entirely. This is different from, say, reverting user customizations to a template, which is much harder to restore through revisions. This is the main nuance between delete and trash actions.
To that end, having quick actions for moving to trash also maintains parity with existing list views:
Anecdotally, I use the trash button there all the time.
I would even go as far as saying that there shouldn't be a modal confirm action when deleting a page. Perhaps we can keep it if the page is published, but if it's just a draft, it should just move it to trash, which is easily visible in the left navigation sidebar:
Removing this modal would also maintain parity with existing list views. But this would be something to consider exploring separately.
Testing Instructions