WIP: FEATURE Infer props from component

[mhsdesign]

@propTypes {
    text = PackageFactory.AtomicFusion.PropTypes:PropsFromComponent {
        type = "Foo.Bar:Text"
        isRequired = true
    }
}

[mhsdesign]

thats a proplem as we cant use eel here.
either put some logic in PropTypeExceptionHandler to determine if in dev context and fall back to the general exception handler (fusion settings)
or we use context aware objects.yaml and use an interface which we set in @exceptionHandler

[mhsdesign]

we could of course achieve the previous behaviour with aop and \Neos\Neos\Domain\Service\FusionService::setPrependFusionIncludes

[mhsdesign]

naming is WIP too - when we find a fitting name i will extract the prototypes into its own folders

suggestion by martin:

• PackageFactory.AtomicFusion.PropTypes:ForComponent and PackageFactory.AtomicFusion.PropTypes:ForComponentArray

[mhsdesign]

i find PackageFactory.AtomicFusion.PropTypes:ForComponentCollection tempting, as i would name my php collection dto like that...

or we could also play with the words infer and props - they are common in typescript / js

or similar to React.ComponentProps<MyComponent>?

[mhsdesign]

Prop.Types:FromComponent
PackageFactory.AtomicFusion.PropTypes:PropTypesFromComponent

we could also use a prop isIterateable = true instead of adding a second prototype for array

[mficzel]

Ups did not see that. However i kinda like the fusion implementations from the other pr a little better