- Issue created by @mxh
- Assigned to mxh
- 🇩🇪Germany mxh Offenburg
Since the field access event allows to bypass the field name, this is considered to be a bug.
- @mxh opened merge request.
- Issue was unassigned.
- Status changed to Needs review
over 1 year ago 1:14pm 13 March 2023 - Status changed to RTBC
over 1 year ago 3:51pm 15 March 2023 - 🇩🇪Germany jurgenhaas Gottmadingen
Nice !
This reminds me that there are 2 strategies to provide token data, both of which used in ECA: it's the data provider interface as used here and it's event subscribers elsewhere. Is there a need to clean that up eventually?
- 🇩🇪Germany mxh Offenburg
Is there a need to clean that up eventually?
Definitive yes, which is worth being handled as its own issue. If I remember correctly, the
DataProviderInterface
approach was added later than event subscribers, and that's the reason why we currently have a mix-up. For that rework, it may also make sense to consider a (static?) "declarative" method for theDataProviderInterface
. With a declarative method, we may be able to expose available tokens that come from events (and event other plugin types) in the modeller UI. -
jurgenhaas →
committed 44290f6b on 1.2.x authored by
mxh →
Issue #3347150 by mxh, jurgenhaas: eca_access: Determining entity field...
-
jurgenhaas →
committed 44290f6b on 1.2.x authored by
mxh →
-
jurgenhaas →
committed da934c6c on 1.1.x authored by
mxh →
Issue #3347150 by mxh, jurgenhaas: eca_access: Determining entity field...
-
jurgenhaas →
committed da934c6c on 1.1.x authored by
mxh →
- Status changed to Fixed
over 1 year ago 10:09am 16 March 2023 - 🇩🇪Germany jurgenhaas Gottmadingen
Created 📌 Make all token data providers discoverable and expose them in the UI and in the ECA Guide Active to follow-up on the DataProviderInterface approach and merged/backported the MR.
Automatically closed - issue fixed for 2 weeks with no activity.