While #3222947: Decide whether to move Quick Edit to contrib discusses deprecating the QuickEdit module for removal from core in 10.0.x, a smaller first step is to remove QuickEdit from the Standard profile, which is a backwards-compatible change that can be made in 9.3.x.
Remove QuickEdit from the Standard profile.
TBD
N/A aside from title.
TBD
TBD
The Quick Edit module is slated for removal from core in Drupal 10. To this end, Quick Edit has been removed from the Standard profile in Drupal 9.3.0. This change does not affect existing sites, only new sites installing the Standard profile for the first time. For more information, see the change record on Quick Edit's removal from the Standard profile.
Show commandsStart within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #3
xjmComment #4
xjmComment #5
dwwCode looks good. Extremely simple config changes. Bot is happy.
Initial CR: https://www.drupal.org/node/3227039 - but it probably needs a little more love that I gave it to start. ;) Changing tags accordingly.
Doesn't this need a product manager sign-off?
Should we assign this to @Dries?
Probably RTBC is premature, but +1 to that.
Comment #6
andypostIt could depend on issue to show deprecated at status report
Comment #7
andypostComment #8
dwwBut this issue isn’t about a depreciation, per se. just reflecting a decision we don’t want to keep enabling Quick Edit by default in Standard.
Comment #9
xjmThis doesn't need a separate product manager signoff from #3222947: Decide whether to move Quick Edit to contrib (one should be forthcoming there shortly!).
The contrib project should also technically be in place for the deprecation to be added, so that could be a separate scope as well potentially as it will be blocked on figuring some things out in #3227033: Remove Quick Edit from core.
Comment #10
xjmComment #11
catchDries signed off on #3222947: Decide whether to move Quick Edit to contrib so we are unblocked here.
Deprecating should definitely be a separate issue I think since it may involve updating test coverage.
Comment #12
xjmWe can however probably use the same CR both for the deprecation and for the removal from Standard profile. To that end, I've attached the CR for this issue to the policy issue as well, and updated the text a bit. Also added the release note.
Comment #13
xjmComment #14
dwwThanks for the CR updates / edits. Reviewed carefully and that looks perfect. 0 complaints or nits.
Release note snipped also looks good.
MR is still clean / simple, bot is happy.
Everyone signed off. No remaining "Needs X" tags. Hence, RTBC!
Thanks,
-Derek
Comment #15
xjmComment #17
effulgentsia commentedNice that it's that straightforward of an MR!
Pushed to 9.3.x and published the CR.
Comment #18
xjmComment #19
xjm