Introduction (copied from Referencing Fields by their names instead of Fully Qualified Classname)
Currently one has to type fully qualified classname in order to define a field in any configuration such as
However, fully qualified classnames are hard to remember and verbose. If we were to simplify/reduce the verbosity from the configuration, our configuration files would look much nicer and compact as well as It wouldn't be a hassle to remember which definition is coming from which class and hence its fully qualified class name. The ticket of DEV-338 - Getting issue details... STATUS is created to tackle this problem and MGNLUI-3882 - Getting issue details... STATUS to implement it. Perhaps for the time being It may seems like we are only targeting fields ,however, the solution which comes up from the discussion regarding the fields should/could be applied relatively easy to the other parts of Magnolia configuration such as actions.
Possible solution at the component provider level
- Add method to resolve alias to Component provider
- Adjust M2B and N2B.
- Add alias property to TypeMappingDefinition
We currently don't have any tooling for module its components/implementations definitions so we could tackle this at the same time.
although I don't see a problem even without a tooling for now if we document it (in the end it's just alias per field here).