Let the caller decide which format(s) to export about fluid-documentation-generator HOT 1 OPEN

I like this idea, but the way I see the dependency architecture it makes more sense with packages that provide various additions - for example, smoother ways to use the CLI or additional exporters. Taking the RST generator and Symfony CLI ideas, those would in my mind be two different packages:

• xyz/fluid-documentation-generator-rst which adds a new exporter
• xyz/fluid-documentation-generator-cli which provides a Symfony base for commands

If/when the latter package was created I would have no worries adding it to suggests and removing the native dumb-style CLI from this package. I would love to not have any CLI capability in this package itself, so it can focus 100% on providing a nice extensible API for the generating engine itself. The end goal being to not make such decisions for people integrating it, but allowing them to pick any number of user-interface-level packages to run the engine.

How does this sound to you?

from fluid-documentation-generator.