TASK: Relax version constraint and allow Neos.Fusion.Form 2.0

[mficzel]

Starting with Neos 5.2 the Neos Package required Neos.Fusion.Form ^1.0 instead of * which will not allow to use version 2.0+ of said package.

This change adjusts the constraint to ^1.0 || ^2.0 to allow projects to benefit from the Fusion.Form Runtime.

Hint: When upmerged to master constraint should be adjusted to ^2.0. If this is forgotten i will take care in a second pr.

Relates: neos/fusion-form#42

[albe]

Question: Is 2.0 b/c with 1.0? I guess someone running composer update would otherwise end up with getting v2 installed and his forms no longer working in a patch-level release?

[mficzel]

@albe there is only a minor change that does not affect Neos.

!!! This change contains a breaking change to version 1.0 as a naming inconsistency was detected !!!
The key form.fieldNamePrefix of the formDefinition has to be changed to form.namespace now. It is quite unlikely that anyone is affected as this never worked as documented and was seldom used anyways since usually the namespace is determined by the request.

So for Neos updating to 2.0 is fine. Also Neos 5.0 and 5.1 require Fusion.Form * which will also fetch the update anyways.

[albe]

Just noticed the When upmerged to master constraint should be adjusted to ^2.0. If this is forgotten i will take care in a second pr. hint when creating the release notes and now saw it was striken through - is this still something todo or not necessary any more? If so, why?

[mficzel]

@albe It is not necessary. Neos demo needs and requires 2.0 and Neos itself can run with both. So the current solution is actually more correct