-
Type: Improvement
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: NoFixVersionApplicable
-
Component/s: Studio Designer
-
Epic Link:
-
Tags:
Context
As part of the Multilayer project, we need to establish an import process for the Designer side assets of dependencies.
As a first step we should validate the current functioning of the import for Designer assets of dependencies. To better understand :
> What is the current behaviour
> Outline possible evolutions
As a second step, we will work with the UI team to validate a definite process for the import of Designer assets in the context of Multilayer
To do
1. PoC => Set-up a testing environment with dependent projects at 3 levels.
This should be a long term env, as it may be used by the UI team in the future
Each project should contribute
- Features
- Layouts
- HTML elements (buttons)
2. ENDPOINT => Review the current endpoint that recovers Designer assets to ensure that all the Designer assets from dependencies are loaded
PoC Objectives :
- UNDERSTAND : If I declare a dependency A, dependency A has a further dependency B, will I see the Designer assets from both A and B imported ?
- UNDERSTAND : (deployment order) If I have the same feature in the dependencies A and B (Feature X and Y), and each feature has a layout
> Will I see feature X as active, feature Y as overridden in modeller ?
> Will I see only the layouts for feature X ?
> Will I see the HTML elements for X and Y
We will be able to investigate further questions with this PoC once the above are answered
- Is referenced in