Rewrite to use core's Default Content API

Created on 28 June 2024, 2 months ago
Updated 24 August 2024, 15 days ago

Problem/Motivation

Drupal 10.3+ include the new Recipes APIs, including a new API for default content:
https://www.drupal.org/node/3445169 β†’

Proposed resolution

Build Drush functions to export content in a format that works with core's Default Content API.
Add Drush functions to recreate existing exported content in the new structure.

Remaining tasks

Build Drush functions to export content in a format that works with core's Default Content API.

User interface changes

All output would use core's Default Content APIs.

API changes

TBD

Data model changes

TBD

πŸ“Œ Task
Status

Needs work

Version

2.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States DamienMcKenna NH, USA

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @DamienMcKenna
  • πŸ‡¨πŸ‡­Switzerland Berdir Switzerland

    The format that core uses is identical to default content, we don't need to rewrite it.

    It's still internal, but we can try running our tests against the core implementation.

  • Status changed to Needs work 15 days ago
  • πŸ‡¨πŸ‡­Switzerland Berdir Switzerland

    Started with an initial test of replacing the importer completely. Tests are failing, one case seems to be that it doesn't like non-existing fields.

    A more feasible approach is likely to wrap it inside since the API has changed, that should make the transition easier, and we could then look into deprecating our API.

  • First commit to issue fork.
  • πŸ‡«πŸ‡·France andypost

    rebased on top of latest 2.0.x and except changes in \Drupal\default_content\Importer::importContent() looks it no longer can import hal_json which means that's 3.x material

    PS: Using PHP 8.4 showing lots of warnings so filed πŸ“Œ [PHP 8.4] Fix implicitly nullable type declarations Needs review

Production build 0.71.5 2024