Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
@Dries in #1978910-62: Convert layout_page_view to a Controller:
Given that we're pretty much at the end of the development cycle and layout module isn't actually used it core, it may be better to remove layout module from core? Thoughts?
@EclipseGc in #1978910-66: Convert layout_page_view to a Controller:
I agree this should absolutely be removed before 8.0 (or sooner) if we don't have code that is using it
Comment | File | Size | Author |
---|---|---|---|
#10 | layout-remove-10.patch | 63.64 KB | effulgentsia |
#3 | remove-layout.patch | 62.54 KB | tstoeckler |
Comments
Comment #1
effulgentsia CreditAttribution: effulgentsia commentedPostponing and tagging "revisit before release" per request in #1978910-66: Convert layout_page_view to a Controller. Also, I tagged this "Approved API change", since per the issue summary, Dries suggested the removal to begin with.
Comment #2
catchIf we're going to do this, I'd rather do it asap rather than later. Removing a module is considerably harder than adding one. Once we get to beta we'll support beta-beta upgrade paths - so what happens if we remove the module on a site that has it enabled?
Comment #3
tstoecklerThis is a simple git rm -r core/modules/layout. I grepped for "layout" in core and couldn't find anything related.
modularity++
Comment #4
effulgentsia CreditAttribution: effulgentsia commentedPatch looks good. Raising priority and tagging as upgrade path related per #2.
Comment #5
webchickDries agreed to postpone this to give SCOTCH folks more time, so it seems like he should be the one to commit the patch if he feels enough time has passed.
Comment #6
Bojhan CreditAttribution: Bojhan commentedJust wondering, if this makes sense when we do start using it with the #2055853: [meta] Improve the place block UX; Separate interaction from the create block UX; Improve the existing blocks-by-theme layout. This needs some more management.
Comment #7
tim.plunkettWe're not using it. That issue is about "Improve the existing blocks-by-theme layout". Not "Improve the existing blocks-by-layout layout".
Comment #8
tstoeckler@Bojhan: Perhaps you meant #1787956: Make blocks relate to layout instances instead of themes, but that got pushed to D9 recently.
Comment #9
webchickI just committed #1978910: Convert layout_page_view to a Controller, so this'll need a re-roll.
Comment #10
effulgentsia CreditAttribution: effulgentsia commentedSame git command as in #3.
Comment #11
webchickProbably fine to go straight back to RTBC on this. If 'bot disagrees, it'll kick it back.
Comment #12
Dries CreditAttribution: Dries commentedCommitted to 8.x. Thanks. Sad to see the module go but we can add it back in in Drupal 9.
Comment #13
BerdirWhat should we do with https://drupal.org/node/1813372 now, delete? edit? Post a new one?
Comment #14
catchHas to be either delete + new one or edit the existing one for change notice, not sure which is best.
Comment #15
star-szrI vote for delete + new so that it gets to https://twitter.com/drupal8changes, RSS, etc.
Comment #16
jibranDo we have to reopen #1787846: Themes should declare their layouts and move it to D9?
Comment #17
EclipseGc CreditAttribution: EclipseGc commentedI think so yes, I also support deleting the old CN and adding a new one that documents this change. No one should come across the old one while trying to upgrade their modules to D8. (we might want to consider some sort of "removed" tag for any other instance of CN's who's underlying code has been removed?)
Eclipse
Comment #18
webchickCool URIs don't change
I just blanked the date to put it back at the top of the list with "[REVERTED]" in the title, and gave a pointer to https://drupal.org/project/layout. Also moved all the active layout.module issues there and will delete the component in a sec.
I'll go commit the old code from D8 core to the contrib project there momentarily.
Comment #19
webchickComment #20
webchick