Specify TYPO3 v10 support in composer.json

[EcoGabe]

No description provided.

[opi99]

Doesn't the BW compatibility break by removing the mixin?

[EcoGabe]

I've just been making my own instance compatible, I didn't intend to make more changes to this PR (else it should be renamed v11 support).

That being said... since mixins are just shortcuts for importing configuration from another file, shouldn't it still work with older versions of Typo3? I just replaced the mixin with the Yaml configuration the mixin contained/referred to. I would still be interested in upstream being compatible with the latest versions of Typo3, if that's a possibility.

[opi99]

Yes and no, they are needed. IMHO you can leave the mixin line untouched for TYPO3 v10/v11 support

[EcoGabe]

It would be nice if mixins did not require a definition. Unfortunately, leaving the mixin line untouched causes errors in v11 because it does not exist

[opi99]

Uhhh, so, need to check another project, IMHO I leave it in. :-/