Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[EAK-457] Add field-level MSM inheritance for authoring dialogs #457

Open
liubou-masiuk opened this issue Jun 15, 2023 · 0 comments
Open
Labels
AEM AEM-specific competencies are involved Java Java code contribution javascript JavaScript code contribution

Comments

@liubou-masiuk
Copy link
Collaborator

Currently, the user can only lock/unlock MSM inheritance on the whole component. Sometimes there is a need to do it for just 1-2 fields and leave the inheritance on the rest of the component

There is a POC of this solution that is based on field-level inheritance in page properties. it can be adapted and released as an open-source solution

Assumptions:

  • field level inheritance will work closely with DependsOn and we will assume that DependsOn is always installed together with field-inheritance

Risks:

  • need to review the overrides we've made for Granite to enable field-level MSM, try to understand if we can do without them or perhaps change them to something less dangerous

Questions:

  • this feature needs to be optional for the end-user. how can we turn it off (presumably by adding/not adding inheritance markers on dialog fields)? how will it be configured by the toolkit users?
@liubou-masiuk liubou-masiuk added this to To do in Development tasks via automation Jun 15, 2023
@liubou-masiuk liubou-masiuk added javascript JavaScript code contribution Java Java code contribution AEM AEM-specific competencies are involved labels Jun 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AEM AEM-specific competencies are involved Java Java code contribution javascript JavaScript code contribution
Projects
Development

No branches or pull requests

1 participant