TASK: Extract hardcoded fusion path

[dfeyer]

The hardcoded values are extracted to Settings.yaml. This change allow the usage of custom Fusion prototype in the rendering.

Fixes #9

[bwaidelich]

@dfeyer Nice one, thanks a lot for this. Would you be up for adding a short paragraph to https://github.com/neos/form-fusionrenderer/blob/master/README.md explaining the new feature?

[bwaidelich]

I'm just wondering: Do we really need such a fine granular configuration?
If we used a setting similar to Neos.Neos.fusion.autoInclude (= package based) this would get quite a bit simpler. What do you think?

[dfeyer]

Most form are uncached, so I think it's nice is we can load just the required fusion. For two recent projet, I just need one or two new fusion object, but I load the full package, I load tons of fusion prototype that are not need for form rendering. Without a granular configuration I need to create a separate package ... that can work too.

get quite a bit simpler

Neos:
  Form:
    FusionRenderer:
      fusionPathPatterns:
        My.Package:Private/Form: true

It's simple ;)

@bwaidelich So the question is more did we want a consistent configuration ...

[bwaidelich]

true. I'm fine with both

[bwaidelich]

Thinking about this one again.. Maybe we could use the glob syntax that we use for includes from Fusion, too!?

[daniellienert]

Since Neos 5.0 the FusionView::setFusionPathPatternsexpects a root.fusion in its path versus globbing the complete path. So this solution would not work as it is now. I suggest to extend the fusion paths with #21

[daniellienert]

Will not work with Neos 5.x

[daniellienert]

Hey @dfeyer, thanks for the PR. Due to changed in Neos 5, #21 was merged as a replacement for this.