That is to say, if the "phpunit.strategy" setting is not a string, then it's
assumed to be a custom strategy.
This would then still allow us to configure the setting "phpunit.prepend_cmd",
but would prevent us reusing an existing strategy i.e. building on top of an
existing strategy.
Allows for future configuration of strategies, should it be needed. Both of the
above could be valid.
The first just implies the command because the type of value is a list i.e. no
additional configuration for the strategy. The second opens up the possibility
of additional strategy configuration, if avaiable in the future.
Re https://github.com/gerardroche/sublime-phpunit/issues/92#issuecomment-1665030486
Allow creation of custom strategies.
Since 3.17.1 you can roughly create custom strategies.
Example: Custom cmd.exe strategy
Command Palette → Preferences: PHPUnit Settings
The "external" strategy is available since 3.17.1 and prevent the exec output panel from opening.
A better api might be something like:
Or simply:
That is to say, if the "phpunit.strategy" setting is not a string, then it's assumed to be a custom strategy.
This would then still allow us to configure the setting "phpunit.prepend_cmd", but would prevent us reusing an existing strategy i.e. building on top of an existing strategy.
Flexible.
Allows for future configuration of strategies, should it be needed. Both of the above could be valid.
The first just implies the command because the type of value is a list i.e. no additional configuration for the strategy. The second opens up the possibility of additional strategy configuration, if avaiable in the future.