As a develop,
I want to only see the adaptation options that I should be using based on the original application,
so that I adapt Fiori elements and OVP based applications correctly
Description
The purpose of this feature request is to reach parity with existing ADP tooling BAS. Currently, the isOVPApp and isFioriElement flags configured in the .adp/config.json allow (de)activating some editing options based on the templating used in the application. We need a corresponding way to configure the same.
Technical Design
We don't need these additional settings, but can get the information from the manifest that is loaded on start of the preview-middleware. This settings can then be exposed to the client-side coding using the flexSettings object. And, then the control properties editor needs to react to them.
As a develop, I want to only see the adaptation options that I should be using based on the original application, so that I adapt Fiori elements and OVP based applications correctly
Description
The purpose of this feature request is to reach parity with existing ADP tooling BAS. Currently, the
isOVPApp
andisFioriElement
flags configured in the.adp/config.json
allow (de)activating some editing options based on the templating used in the application. We need a corresponding way to configure the same.Technical Design
We don't need these additional settings, but can get the information from the manifest that is loaded on start of the
preview-middleware
. This settings can then be exposed to the client-side coding using theflexSettings
object. And, then the control properties editor needs to react to them.Acceptance Criteria
GivenWhenThen format (https://martinfowler.com/bliki/GivenWhenThen.html)
Given I have a Fiori elements or OVP based application... when I start the editor then I will only have access to allowed change functionality.
Notes
Tasks