Problem/Motivation

I'm finding it increasingly difficult to make iterative changes to code I *know* is going to move.

For example, as soon as #2286357: Introduce Display Variants, use for the block rendering flow goes in, we'd have to refactor around those changes.
Additionally, as soon as that goes in, I'm opening an issue to add a basic entity to replace the way blocks are handled.

Proposed resolution

Move all of the code we plan to move to core into a new submodule.
This will give us a better picture of what we can or can't change, and what page_manager might actually look like.

Remaining tasks

Someone needs to tell me this isn't a terrible idea.

User interface changes

N/A

API changes

Everything I want to go into core will move into a display submodule.

CommentFileSizeAuthor
#1 pm-2289533-1.patch85.36 KBtim.plunkett
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

tim.plunkett’s picture

FileSize
85.36 KB
tim.plunkett’s picture

This would also help spot patches that add new functionality to code destined for core, which would let us be more cautious.

mglaman queued 1: pm-2289533-1.patch for re-testing.

Status: Needs review » Needs work

The last submitted patch, 1: pm-2289533-1.patch, failed testing.