ionic-team / ionic-team/ionic-cli

Revert removal of `--no-open` flag to `ionic cap run`.

Abierto
#4,716 0 comentarios 0 reacciones 0 asignados Ver en GitHub
triage
Lenguaje dominante
TypeScript
Estrellas
2k
Forks
682
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

The capacitor 3 support added to the CLI changed the behavior of `ionic cap run`. It now does one of two things to "launch" the native project:
- Deploy it directly to a target emulator (either with the `--target` flag or interactively)
- Run `cap open` to open the native project

However, I would like it to do neither of these things. My previous workflow used the `--no-open` flag to use `ionic cap run` to simply manage the angular build server and the syncing of the `capacitor.config.json`, and then I manually executed the native part of the build process (which is necessary for my project, as it has many different schemes/flavors to build). I would like to request that this workflow continue to be supported. The currently available `--open` flag is less than ideal, because it will spawn a new Android Studio process every time it's executed.

Thanks for all your hard work on this project!

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.