Improve batches so that we only create 1 revision for each entity being updated or removed

Created on 19 March 2025, 17 days ago

Problem/Motivation

Paragraph entities are processed after all the other entities so that we can update the host entity. πŸ“Œ Save paragraphs as part of a host entity save Active changed how paragraphs are saved but didn't resolve the fact that if a node has link to another entity in field directly connected to the node and in a paragraph connected to the node this will result in two saves of the node. One to update the field and one to update the paragraph.

Proposed resolution

Change it so that we process paragraphs first to find the host entities. Then when we process the non-paragraph usages if the is a match with a paragraph host entity updates the paragraphs at the same time as the field. Finally we will need to process all the paragraph host entities that didn't all have a field. This will reduce the number of revisions this module can result in.

Remaining tasks

User interface changes

None

API changes

TBD

Data model changes

None

πŸ“Œ Task
Status

Active

Version

1.0

Component

Code

Created by

πŸ‡¬πŸ‡§United Kingdom alexpott πŸ‡ͺπŸ‡ΊπŸŒ

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

Merge Requests

Comments & Activities

Production build 0.71.5 2024