Start passing entity type/entity ID context to SdcController from the FE

Yes, please!

\Drupal\experience_builder\Controller\SdcController::layout() has this horribleness:

  public function layout(): JsonResponse {
    $first_article = Node::load(1);
    if (!$first_article || $first_article->getType() !== 'article') {
      throw new \LogicException('For now, this assumes node 1 exists and is an article!');
    }

    assert($first_article->field_xb_demo[0] instanceof ComponentTreeItem);

    $tree = $first_article->field_xb_demo[0]->get('tree');
    assert($tree instanceof ComponentTreeStructure);

    $hydrated = $first_article->field_xb_demo[0]->get('hydrated');
    assert($hydrated instanceof ComponentTreeHydrated);
    $hydrated_json = $hydrated->getValue()->getContent();

That's something that this should remove 🤓

(Thanks for creating this issue!)

I'm running into this too over at 📌 Evolve component instance edit form to become simpler: generate a Field Widget directly Fixed .

Ensuring this shows up on https://contribkanban.com/board/experience_builder.

Are these commit messages auto-generated and random? 🤪🤣

The MR indicates that this depends on 📌 Clarify if local dev on /ui should be possible without Drupal Needs review , reflecting that.

📌 Clarify if local dev on /ui should be possible without Drupal Needs review should land first, but that didn't stop me from reviewing 😊

Are these commit messages auto-generated and random?

Na, I'm just having fun with portlandia quotes

The back-end changes here (in the controllers + *.routing.yml) make sense.

The front-end changes I'd like to be reviewed by either @bnjmnm or @jessebaker 😊

FE looks good

This caused a small regression, which 📌 Introduce `hook_storable_prop_shape_alter()`, use it to prefer the Media Library widget for "image" PropShape if Media Library is installed Fixed surfaced. Fixed by removing one character in https://git.drupalcode.org/project/experience_builder/-/merge_requests/1...

This introduced a regression: 🐛 Regression caused by #3462247: `configure` route in *.info.yml needs params Active .

Automatically closed - issue fixed for 2 weeks with no activity.