Introduce new command dev in project group which will:
start the project's sandbox in dev mode (same as sandbox start --dev)
execute gradlew dev command for the project/app (same as project gradle dev. Yes, this task should be configured in the app's build.gradle and we'll do that for all of our starters.
TBD: gradlew dev is a non-exiting command, just as sandbox start. Which means we have to start the sandbox in the background (same as what --detach does), then run the gradlew dev task.
Special cases:
Project doesn't have a sandbox yet. If user executes "project dev" inside a project that doesn't have a sandbox yet, remember to start the sandbox in "dev" mode when it's created and user answers "Yes" to the question about starting it.
Project's sandbox is already running. Show a message "Sandbox <sandbox_name> is already running. Make sure it's running in dev mode or stop it and re-run the command." and don't attempt to start the sandbox.
Introduce new command
devinprojectgroup which will:sandbox start --dev)gradlew devcommand for the project/app (same asproject gradle dev. Yes, this task should be configured in the app'sbuild.gradleand we'll do that for all of our starters.TBD:
gradlew devis a non-exiting command, just assandbox start. Which means we have to start the sandbox in the background (same as what--detachdoes), then run thegradlew devtask.Special cases:
Sandbox <sandbox_name> is already running. Make sure it's running in dev mode or stop it and re-run the command." and don't attempt to start the sandbox.