Possible ECA config entity optimisations

Created on 16 December 2024, 6 days ago

Problem/Motivation

This is a late call, but it will be just meta-data and has no functional impact whatsoever.

ECA models in various recipes will be part of Drupal CMS 1.0 - and they have 2 areas of optimisation:

1. Version number: each ECA model has its own version number. This is purely informational and has no update or even auto-update relevance. It's just to identify which version of a model is installed somewhere, in case somebody asks for support. By default, we set such version strings to 0.0.0. Should we change those strings to 1.0.0?

2. XML data: each ECA model comes as 2 config entities, an eca.eca.MODELID and an eca.model.MODELID file. The former contains the required config, the latter contains proprietary XML data just in case somebody wants to edit and modify that ECA model. Now, we've enhanced ECA such that the XML data can be re-generated!!! That said, we don't have to deliver those second files any longer. Shall we remove the XML files from all recipes?

πŸ“Œ Task
Status

Active

Component

General

Created by

πŸ‡©πŸ‡ͺGermany jurgenhaas Gottmadingen

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