Closed (fixed)
Project:
Drupal core
Version:
8.8.x-dev
Component:
node system
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
23 May 2019 at 12:20 UTC
Updated:
21 Jun 2019 at 09:29 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
pasqualleComment #3
pasqualleComment #4
idebr commentedNice find!
Attached patch adds test coverage. Interestingly it did not fail because 'Delete' partially matches 'Delete content type'.
Comment #6
pasqualleComment #7
pasqualleThe code works now, but I am thinking if we should not just have "Save" and "Delete" action labels. As I see no other entity cares to modify the labels in core or contrib..
Comment #8
pasqualleComment #9
idebr commentedI suggest we move the question "Should the entity type be mentioned on the save/delete button?" to a followup issue and keep this scoped to a simple bug fix. The intended UX was developed a long time ago (see #111715: Convert node/content types into configuration where the current code was implemented back in 2013).
Comment #10
pasqualleok
Comment #17
gogowitsch commented+1: Patch & test look good to me.
Comment #24
idebr commentedReupload of #4 to reduce testbot clutter.
Comment #25
alexpottLet's remove the line instead. No changes to the UI, no changes to tests, and consistent with the very similar vocabulary edit screen.
Comment #26
init90Sounds logical. Updated according to last comment.
Comment #27
idebr commentedComment #28
alexpottChanging the title to reflect what's happening here.
Comment #29
alexpottComment #30
alexpottCommitted and pushed 8ca1b5a7c5 to 8.8.x and 9c815fd316 to 8.7.x. Thanks!
As this code is not used I've backported this to 8.7.x to keep the branches in-sync. I spent a bit of time trying to find an issue about standardising these buttons but then realised that even if this the new standard would be for this button to read
'Delete content type'then we'd need to handle that change correctly. And this code is still dead. So removing it now is fine even if we decided to change the button text at a later date.It'd be great if someone could try to find that issue about standardising button texts because I think we probably should open a follow-up to completely remove the method override here.