[make:webhook] Add new command for Symfony's Webhook Component

[maelanleborgne]

Add a maker that would help create a webhook :

• Create a RequestParser extending AbstractRequestParser and interactively define the RequestMatcher(s) to use.
• Create a WebHookConsumer implementing ConsumerInterface with the #[AsRemoteEventConsumer] attribute.
• Add an entry to config/packages/webhook.yaml with the name of the webhook + the RequestParser service name + empty secret with an instruction on how to set it (as a comment).

That is an easy scaffolding command but since Webhook is a quite recent component and the documentation is pretty scarce right now, I think it would make sense to have a maker to help setting things up.

Regex: https://regex101.com/r/S3BWkx/1

Bumps test process timeout from 10 to 30 seconds - composer is a bit slow on Windows.

maker-bundle/src/Test/MakerTestEnvironment.php

Line 339 in 30cdf17

timeout: 10

[jrushlow]

This is looking pretty nifty @maelanleborgne - a few suggestions and I think we'll be in good shape..

[jrushlow]

Do the same for other parts of this maker: Let's add so more spacing within the code. grouping multiple single line variable declarations is A-OK. But using that enter button between multi-line declarations, conditionals, etc... improves readability..

Suggested change

	$choices = array_diff($availableMatchers, $addedMatchers);
	$question = new ChoiceQuestion($questionText, array_values(['<skip>'] + $choices), 0);
	$matcherName = $io->askQuestion($question);
	if ('<skip>' === $matcherName) {
	return null;
	$choices = array_diff($availableMatchers, $addedMatchers);
	$question = new ChoiceQuestion($questionText, array_values(['<skip>'] + $choices), 0);
	$matcherName = $io->askQuestion($question);
	if ('<skip>' === $matcherName) {
	return null;

[maelanleborgne]

This is looking pretty nifty @maelanleborgne - a few suggestions and I think we'll be in good shape..

Thank you for the review. I'm at SFlive right now, I'll try to push the changes on my way back. Just curious about the bit on unit testing the regex : testing invalid cases seems pretty hard with the MakerTestCase, should I make the method public? Use reflection method and invoke maybe?

[jrushlow]

@maelanleborgne The regex test can be added to:

maker-bundle/tests/RegexTest.php

Line 17 in 74a8918

class RegexTest extends TestCase

I'll have to do some minor refactoring on that class to make it "multi-purpose" (ill get a pr up and merged here shortly) - but you should be able to add another test method & dataProvider to that test class and be all set.

As to the regex itself - move the regex string to a constant like:

maker-bundle/src/Test/MakerTestEnvironment.php

Line 25 in 74a8918

public const GENERATED_FILES_REGEX = '#(?:created|updated):\s(?:.*\\\\)*(.*\.[a-z]{3,4}).*(?:\\\\n)?#ui';

Then you can call that regex expression from within the class and within the test without too much trouble.

Tell the folks at SFLive I said hello!

[jrushlow]

Awesome! Thank you @maelanleborgne