Problem/Motivation

We provide a DTO data type that is supposed to handle any sort of data properties, as long as it's passed to it as typed data. This brings the theoretical benefit of having an object holding different field item lists (and configuration values) without losing its parent information, i.e. one DTO may hold multiple properties coming from different sources.

While already working fine for content entities, it is not yet working well for configuration entities and objects. But there is a manager for typed configurations, so a DTO should be capable of handling configuration data in the same manner as it's already doing for content entity fields.

Steps to reproduce

Proposed resolution

Remaining tasks

Make this behavior consistent regarding content as well as configuration. Once this is fixed, we are able to use DTOs for various use cases, e.g. for building custom forms.

User interface changes

API changes

Data model changes

Issue fork eca-3292951

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

mxh created an issue. See original summary.

mxh’s picture

Assigned: mxh » Unassigned
Status: Active » Needs review

MR196 contains the adjustments, with an added method for saving collected data on a DTO. This is just an addition on API-level, that may be seen as a preparation for future feature additions like building forms using DTOs.

jurgenhaas made their first commit to this issue’s fork.

  • jurgenhaas committed 9029304 on 1.0.x authored by mxh
    Issue #3292951 by mxh: Improve handling on level of typed data in DTO...
jurgenhaas’s picture

Status: Needs review » Fixed

Looking good, merged.

Status: Fixed » Closed (fixed)

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