[RFC] Add target option to all commands (dir relative to the project root)

[yceruto]

Related with #2 and #49

What about a new target option for each command that allows us to change the target directory where the final skeleton file is generated?

For example make:unit-test FooTest always creates the file class inside tests/ directory, but as the best practice recommends:

By convention, the tests/ directory should replicate the directory of your bundle for unit tests. So, if you're testing a class in the src/Util/ directory, put the test in the tests/Util/ directory.

Something like this make:functional-test FooTest --target=tests/Util will be great to not move each generated file to the corresponding directory and change its namespace.

[stof]

well, we should rather support passing a namespaced name for the test name, and the location would be derived from it. When moving file around, you generally also want to change the namespace.

[yceruto]

... support passing a namespaced name for the test name, and the location would be derived from it.

@stof do you mean deriving it from composer.json psr-4 autoload configuration?

1. run make:unit-test App\\Tests\\Util\\FooTest (short Util\\FooTest)
2. extract target and NS from composer.json > autoload-dev > psr-4 > "App\\Tests\\": "tests/"
3. generate file in tests/Util/FooTest.php with namespace App\Tests\Util;

?

[yceruto]

Even though for FunctionalTestCommand I'd like to pass (rather than its class name) the path to the file class and generate a better skeleton regarding its parent class/interface (if available).

For example:

• running make:functional-test src/Form/Type/UserType which extends from AbstractType I'd like to generate a functional test like this http://symfony.com/doc/master/form/unit_testing.html
• running make:functional-test src/Repository/UserRepository which extends from EntityRepository I'd like to generate this one http://symfony.com/doc/master/testing/doctrine.html

and so on.