Haehnchen
Feature request: Run/Debug Commands
Hi!
Thanks for an awesome plugin! It really saves me a lot of time every single day!
I would love a little green play button in the margin of commands, next to execute or the class...
Would that be easy to add / quick fix? maybe I could help?
@Haehnchen Is any chance to have Run/Debug for Commands (same as for PHPUnit tests) in near future?
I wonder if it will be way easier to make now if its based on the newish #[AsCommand("app:command:name") attribute!
@Haehnchen While it is awesome we can run commands straight from phpstorm, it's not ideal the way it is implemented right now. We work with docker containers and currently there is no way to configure the plugin to run the command inside a container, so for us the feature is not really useful at the moment.
However, it is in the way of easily clicking through to the configuration of the command. As you can see, the linemarker now replaces the cog for configuration.
Can we perhaps move it to to the $defaulName-line so we can support both?
My bad, turns out this specific command was not yet configured 🙈.
Awesome! Thanks @Haehnchen !
Is it possible to also look for the Attribute #[AsCommand('app:test')] instead of $defaultName?
I see you have added a codeblock for it (https://github.com/Haehnchen/idea-php-symfony2-plugin/pull/1920/files#diff-bd1d67aad9012c45bcb6b02f252d9f007cf79ae6b13cf0f5bbbb643df1b41569R73) but it doesnt seem to work...
I'm running Symfony plugin 2022.1.225, and PHPStorm 2022.1 :)
Thanks for the amazing work, and is there anything I can do to help?
thank you for this hint. i was thinking that the named arguments automatically were resolved by PhpAttribute, but its likely not the case.
name: 'app:test:test' should work.
i will fix this in the next release.
@ChristianVermeulen yes, i was playing also with remote interpreter support like docker, but then stripped the first iteration, as this needed some improvements first, but will be added.