Ensure typed data prototypes are cached according to pipeline

Created on 29 August 2023, over 1 year ago
Updated 1 January 2024, 12 months ago

Problem/Motivation

We have a custom command that batch processes datasets. This issue was identified then, it isn't an issue when processing a single dataset. Drupal's typed data manager maintains a runtime cache of what it calls 'prototypes'. These prototypes are effectively a store of typed data properties organised into buckets. The bucket name is composed of parts, namely the data type, property path and property name. In our case we supplied the data type and property name, but not the path. An example of what this looked like is 'data_pipelines_data::type'. This is an issue because if two pipelines have the same property during execution then the first pipeline's property is used and not the second. My change addresses this by supplying the property path too - 'data_pipelines_data:pipeline_name:type'.

For reference of where it does all this -
https://github.com/drupal/drupal/blob/11.x/core/lib/Drupal/Core/TypedDat...

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

πŸ› Bug report
Status

Fixed

Version

1.0

Component

Code

Created by

πŸ‡¦πŸ‡ΊAustralia mortim07

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

Comments & Activities

Production build 0.71.5 2024