Consider using annotations/attributes instead of stub config entities

Created on 12 December 2024, 6 days ago

Problem/Motivation

The activity/answer plugin handling handles stub config exports with the bundle replaced with a placeholder when adding an activity type.

I'm wondering if we could add extra data to the plugin annotation/attribute, like an array of field names and field types, and then use that to dynamically create the fields on the bundle - this would allow everything to be defined in one place then. Question is how complex would it make the annotation.

No hurry here - if we keep both methods for a while could happen at any point, but wanted to open before forgetting the idea.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Feature request
Status

Active

Version

1.0

Component

Activities and answers

Created by

🇬🇧United Kingdom catch

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

Comments & Activities

  • Issue created by @catch
  • 🇵🇱Poland Graber

    Also not sure about the complexity of installing config that is not config yet.. worth investigating at some point when we'll have time for that.

Production build 0.71.5 2024