You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We really don't need to do that, we just need to ask for it!
$doc = new Respect\Doc();
$doc->fromSources('src/*.php')
->fromTests('/test/*Test.php')
->fromPackages('composer.json', 'phpunit.xml')
->generate();
Using Respect\Foundation outside the CLI is also possible, so the developer can run this:
$libraryFolder = (string) new Respect\Foundation\InfoProviders\LibraryFolder;
(Which reminds me that we should create a fluent interface for Foundation, like f::libraryFolder()).
This bootstrap is their responsibility, we provide both the documentation generator and information provider, the developer binds them both. We can offer him a sample bootstrap or config.ini for ed, but he must know how to bind the components (it's easy!).
As noted by @alganet, Doc is evolving and we need to get some meta information from the project, such as:
We have a lot of ways to do that, a lot of that information is already provided by Foundation so we should use it? Or how should we do it?
Let the discussion flow now =P
PS: Related issues #4, #13 and #16
The text was updated successfully, but these errors were encountered: