Static plugins improvement

[raffaelecarelle]

1. Why is this change necessary?

Easiest scafolding for project related plugin

2. What does this change do, exactly?

• Allow PluginCreateCommand.php to create static plugins
• Allow ThemeCreateCommand.php to create static themes

5. Checklist

• I have rebased my changes to remove merge conflicts
• I have written tests and verified that they fail without my change
• I have created a changelog file with all necessary information about my changes
• I have written or adjusted the documentation according to my changes
• This change has comments for package types, values, functions, and non-obvious lines of code
• I have read the contribution requirements and fulfill them.

[github-actions]

	Warnings
⚠️	The Pull Request doesn't contain any changelog file

[raffaelecarelle]

@shyim then...why not considering to include "custom/static-plugins" directory in PluginFinder and KernelPluginLoader?

Or it just do within another way?

[shyim]

@raffaelecarelle static-plugins are intended to be loaded by Composer. Therefore, they are not considered manually

[raffaelecarelle]

@raffaelecarelle static-plugins are intended to be loaded by Composer. Therefore, they are not considered manually

as I thought...But I think this change it would help anyway to create plugins or themes easier :)

feedback are welcome. thankyou!

[aragon999]

As the static-plugins need the same structure as normal plugins, I guess this is useful. Although it might in general be better to work with (Symfony-)bundles, or directly in the src folder, but then the whole static-plugins should be removed altogether.

So I think as long as the static-plugins are present it might be reasonable to create "static plugins/themes" using the commands.

[aragon999]

Suggested change

	->addOption('static', null, null, 'Create Theme in custom/static-plugins folder');
	->addOption('static', null, null, 'Theme will be created in the static-plugins folder');

[raffaelecarelle]

As the static-plugins need the same structure as normal plugins, I guess this is useful. Although it might in general be better to work with (Symfony-)bundles, or directly in the src folder, but then the whole static-plugins should be removed altogether.

So I think as long as the static-plugins are present it might be reasonable to create "static plugins/themes" using the commands.

I think that too. Thank you

[AydinHassan]

Thanks for the improvement @raffaelecarelle 🎉