Add TypoScript support

[andreaswolf]

No description provided.

[andreaswolf]

One thing to solve here: how should a single Fractor communicate its result back to the caller? There is no clear rule for that right now, so @simonschaufi and me discussed that today. We came to the following conclusion:

• null = don't change anything
• a node or a list of nodes = replace the current node with that
• an integer = do something else (specific to each file type?), e.g. remove the node, stop traversal of the node (and possibly its children)

This is at least similar to what Rector does, probably it's 100% the same; I did not check that again for now.

Compared to the XML Fractor, an additional challenge with TS is that we need to return a list of nodes from the iterator, since there is no document node that will automatically collect all changed nodes (either directly or implicitly in its children). This needs to be solved, but is not a big deal.

Deciding if a node can be handled and recording the changes and who changed what is part of the abstract base Fractor, so it must basically be reimplemented for each file type. That's not easy to change, so we accept that for now (and it leaves us more leeway to adapt things for file types where it is needed).

[andreaswolf]

@simonschaufi I just resolved all remarks that will be fixed by our pipeline. No need to comment those :)

[simonschaufi]

A highly requested feature is missing: formatting the result with space or tab indentation. Can this be configured or is this not possible?

[andreaswolf]

A highly requested feature is missing: formatting the result with space or tab indentation. Can this be configured or is this not possible?

Should be possible, I'll have a look.

[andreaswolf]

A highly requested feature is missing: formatting the result with space or tab indentation. Can this be configured or is this not possible?

I would open an issue and postpone that for now, so we can get this merged now.