[RFC] Release/2.0.0

[dmolineus]

I've started to rework the MetaPalettes extension to support Contao 4.4. Some refactoring to fullfill coding standards are yet missing:

• [x] Move to ContaoCommunityAlliance namespace
• [x] Provide Bundle and Manager plugin
• [x] Add unit tests
• [x] Split monolithic MetaPalettes class into smaller one
• [x] Use PaletteManipulator internally where possible.
• [x] Apply coding standards

Some points should be discussed:

• Should we drop the static manipulator class completely and force people to use the PaletteManipulator? I vote against as it could be a shortcut. Besides removing fields is missing in the PaletteManipulator
• Should we support fallback classes for the old namespaces (at least for the static methods)? I also vote against as it's a new major release and people have to adjust their code anyway.

[zonky2]

@dmolineus it´s only for Contao 4.4?

[dmolineus]

@dmolineus it´s only for Contao 4.4?

Ja.

[dmolineus]

Adressed all requested changes and add more tests for the multi inheritance features.

[discordier]

@dmolineus could you please have a look on my changes in fca3613, b171d08 and 47d2b7a if I might have broken any of your features?

IMO we should address some things regarding the MetaPalettesBuilder, it extends DcaReadingDataDefinitionBuilder which has a static process method which will create an instance. Therefore the DIC defined parser from services.yml will never get used. How shall we proceed here?

[dmolineus]

Looks good so far. Just one thing which I guess that could be simplified.

IMO we should address some things regarding the MetaPalettesBuilder, it extends DcaReadingDataDefinitionBuilder which has a static process method which will create an instance. Therefore the DIC defined parser from services.yml will never get used. How shall we proceed here?

I'll have to take a deeper look how the definition builders are called by the DCG. Would it be possible use a service listener or is there no support for it at the moment?