API Platform support: add an --api-resource flag for the make:entity command

[dunglas]

This PR adds a new --api-resource flag to the make:entity command. It allows to automatically a REST endpoint with CRUD operations for the given resource class using API Platform:

I need some guidance about how to add test for this (actually, a few tests are red locally on my Mac even on master).

Fixes #175.

[weaverryan]

Ignoring your question about testing for a moment, I don't like the --api-resource flag from a user's perspective. I think it only makes sense to add a new interactive question to make:entity automatically IF ApiPlatform is installed.

[weaverryan]

Or, the option AND automatically asking if the flag isn’t passed and API Platform is installed

[dunglas]

@weaverryan done

[weaverryan]

One minor comment. And, we should add a test for this. In FunctionalTest, I would duplicate the entity_new test case that's inside getCommandEntityTests(). There, we can add api as a dependency (so it gets installed) and then interactively answer the new question. To be extra sure, by adding the ->assert(function (string $output, string $directory) { to the test case, you could check the new file for the annotation.

[weaverryan]

We should only ask this question when the entity does NOT exist yet. Unfortunately, that means we'll need to duplicate a bit of logic from generate() up here:

$entityClassDetails = $generator->createClassNameDetails(
    $input->getArgument('name'),
    'Entity\\'
);
$classExists = class_exists($entityClassDetails->getFullName());

[dunglas]

Fixed in d003a48 (with some more Voodoo...)

[dunglas]

Tests added.

I also transformed Generator in a service: it's better from a design POV (this class should be a service anyway), and it prevents to add a new magic interface to be able to retrieve the Generator instance in the interact method.

IMO we should also remove the Generator argument from the MakerInterface::generate() method and recommend using the service instead (it's allowed by our BC policy, and won't break existing external implementation as long a we still pass this argument even if not defined in the interface). But I'll handle that in another PR, because all other makers need to be updated, and it's not related at all with the purpose of this PR.

[weaverryan]

Thank you @dunglas!