You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was thinking about having an infrastructure for executing flow commands to provide an action via the actions menu or line markers (i.e. for .*CommandController->.*Command methods or up and down in node-migrations).
I'm not quite sure if it would be possible to leverage the run/debug configurations (i.e. require the user to set up a run-configuration fitting for the project and then select this configuration in the plugin settings) in a way that actions could add parameters.
The more simple setup would probably be setting a working directory (defaulting to the project directory) and the script name (which could either be something like flow/flow.bat or a custom command to interface maybe with docker, like ddev exec ./flow).
But maybe most people have different approaches already working well.
The text was updated successfully, but these errors were encountered:
I was thinking about having an infrastructure for executing flow commands to provide an action via the actions menu or line markers (i.e. for
.*CommandController->.*Command
methods orup
anddown
in node-migrations).I'm not quite sure if it would be possible to leverage the run/debug configurations (i.e. require the user to set up a run-configuration fitting for the project and then select this configuration in the plugin settings) in a way that actions could add parameters.
The more simple setup would probably be setting a working directory (defaulting to the project directory) and the script name (which could either be something like
flow
/flow.bat
or a custom command to interface maybe with docker, likeddev exec ./flow
).But maybe most people have different approaches already working well.
The text was updated successfully, but these errors were encountered: