Problem/Motivation

In #2296423: Implement layout plugin type in core, plugin.manager.core.layout was chosen as the service ID
layout_plugin.settings was the config schema name chosen for layout plugins.

These were not discussed in depth.

Proposed resolution

Discuss!

Remaining tasks

Change them, or close this issue.

User interface changes

API changes

Data model changes

Comments

tim.plunkett created an issue. See original summary.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

tim.plunkett’s picture

tim.plunkett
he/him
Primary language English
Location Philadelphia
CreditAttribution: tim.plunkett at Acquia commented
Status: Active » Closed (works as designed)

The naming is fine, and has already been adopted by contrib.

jibran’s picture

jibran
he/him
Primary language Urdu
Location Sydney, Australia
CreditAttribution: jibran at PreviousNext commented

For anyone using plugin.manager.layout_plugin from contrib, it is now called plugin.manager.core.layout. This API break was not mentioned anywhere.

tim.plunkett’s picture

tim.plunkett
he/him
Primary language English
Location Philadelphia
CreditAttribution: tim.plunkett at Acquia commented

Layout Plugin still uses the old ID. Which is in contrib. The new ID is a core thing. Not an API break.

https://www.drupal.org/docs/8/api/layout-api/how-to-upgrade-from-layout-... can always be expanded!