Drupal Experience Builder Advances with JSON Querying and Enhanced UI Features

Staff Reporter

Abstract creative homepage illustration — Freepik

The latest development update by Wim Leers for Drupal's Experience Builder (XB) highlights significant progress across various aspects of the project. Ted Bowman made strides in preventing the uninstallation of modules providing field types used in XB by focusing on querying XB's JSON blobs in the database, in line with Drupal 11's requirement for databases supporting JSON querying. Despite inconsistencies across different databases, Brad Jones is enhancing Drupal's database abstraction layer to support JSON, supported by Pitch-Burgh. To ensure compatibility from the start, the XB CI pipeline was updated to test across multiple databases.

Additionally, Ben Mullins and Jesse Baker introduced a tree view in the UI, improving navigation on the canvas, while Harumi Jang added foundational support for undo/redo functionality. Active discussions on the data model and testing frameworks were held during the second asynchronous XB meeting led by Griffyn Heels. By Friday, end-to-end tests verifying key functionalities of XB fields were completed, marking a tangible advancement in the project's implementation.

Click here to follow us on LinkedIn

Source Reference

Title

XB week 4: annotated data model test

Byline

Wim Leers

Date of Publication

12 June 2024

URL

https://wimleers.com/xb-week-4

Disclosure: This content is produced with the assistance of AI.

Comment

Disclaimer: The opinions expressed in this story do not necessarily represent that of TheDropTimes. We regularly share third-party blog posts that feature Drupal in good faith. TDT recommends Reader's discretion while consuming such content, as the veracity/authenticity of the story depends on the blogger and their motives.

Note: The vision of this web portal is to help promote news and stories around the Drupal community and promote and celebrate the people and organizations in the community. We strive to create and distribute our content based on these content policy. If you see any omission/variation on this please let us know in the comments below and we will try to address the issue as best we can.

Drupal