Overview

This is blocked by [##3485878: Server-rendered component instances should NEVER result in a user-facing error, should fall back to a meaningful error instead (+ log)].

#3485878: Server-rendered component instances should NEVER result in a user-facing error, should fall back to a meaningful error instead (+ log) will have added fallback markup + logging.

This issue should expose it as structured information for the client.

Proposed resolution

Add a JSON:API error object in the API responses for ApiLayoutController::(get|patch|post).

User interface changes

None.

Comments

wim leers created an issue. See original summary.

wim leers’s picture

Issue summary: View changes
Issue tags: +Needs tests, +stable blocker
wim leers’s picture

Title: [PP-3] Server-rendered component instances failing to render should expose the meaningful error to the XB UI in a structured way » Server-rendered component instances failing to render should expose the meaningful error to the XB UI in a structured way
Status: Postponed » Active

Unblocked!

lauriii’s picture

Issue tags: -stable blocker

Project: Experience Builder » Drupal Canvas
Version: 0.x-dev » 1.x-dev

Experience Builder has been renamed to Drupal Canvas in preparation for its beta release. You can now track issues on the new project page.

wim leers’s picture

Title: Server-rendered component instances failing to render should expose the meaningful error to the XB UI in a structured way » Server-rendered component instances failing to hydrate/render should pass a meaningful error in API responses to the Canvas UI/client in a structured way