[2.0.0-beta4] Evolution of DeriableContexts : refactor code with source plugin manager, add several contexts in derivation, and better support prop types

Created on 30 September 2024, 10 months ago

Problem/Motivation

  • Refactoring of source plugin context and tag filtering capabilities in a trait for sources and derivable contexts :
    Part of the code we have added to the ui patterns source plugin manager can be put in a more convenient way into a Trait. So that, other plugin manager would benefit from those functionalities, especially the DeriableContext plugin manager, which will be used by different sources (data from field, data from referenced entities..etc) to gather derivable contexts with conditions
  • Before the introduction of a new source to gather data from referenced entities 🐛 [2.0.0-alpha2] Field Formatters: Re-enable the source plugin entity reference Active , we need to update the interface for derivable plugin and their use, so that a derivable context can return multiple derived contexts instead of one. it can return 0 to n
  • When using for example the source data from a field, all derivable contexts are listed even if the selection of a context will lead to zero compatible sources. We need to introduce a mechanism to tackle this in advance, so that only relevant contexts are shown
📌 Task
Status

Active

Version

2.0

Component

Code

Created by

🇫🇷France just_like_good_vibes PARIS

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