Issue Feature New Orphaned

#109396Reactions from file configuration

Mathias Brodala 03/27/26, 08:57 updated 03/27/26, 16:47

Description

The Reactions extension currently allows creating reactions as database records. Extensions can register reaction types.

Various disadvantages arise from the DB-based management:

1. No automatic deployment of new/changed Reactions: an admin must create/update reactions manually after deploying the related code. This can lead to delays or errors in the meantime.
2. Risk of outdated/unsynced Reactions in multiple environments: in addition to production there are often other environments like staging, testing, etc. These must be kept in sync manually to ensure reliable and predictable behavior.
3. Harder automated tests due to unknown secret: secrets of Reactions are known only once on creation. Writing realistic automated tests for existing Reactions requires replacing the secret with a static, predefined value.

Given these facts it would be useful if Reactions could also be registered via file configuration. This is similar to form definitions which can be defined as files and (since #108653) as database records. Other examples are purely file-based like site configurations. All of these have in common that they are basically code/infrastructure/setup without actual user content.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

Fix this issue

Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". How to create a patch

Commit message
[FEATURE] Reactions from file configuration Resolves: #109396 Releases: main