Yep I think this is a fine addition. Can one of you fine gents file an issue?
I am just catching up on CLI issues - lots of work to do! If anyone wants to lend a hand feel free to dive into the CLI-tagged issues. Anything not set to "In Progress" is up for grabs. On 7/24/13 7:38 AM, "David Kemp" <[email protected]> wrote: >Further to this, the low-level run script calls build, so the current >behavior of run is prepare, compile, deploy > >For my purposes, I don't object to 'build, deploy' as a step - but I need >to skip prepare. > > > > >On Wed, Jul 24, 2013 at 10:05 AM, Tommy Williams <[email protected]> >wrote: > >> Yeah, seems odd that prepare,compile is nearly impossible to avoid. >> On 24 Jul 2013 07:03, "Ian Clelland" <[email protected]> wrote: >> >> > I think what I'd like to see is this: >> > >> > cordova run <platform>: prepare, compile, deploy >> > cordova deploy <platform>: deploy only (existing compiled app) >> > >> > Then we can make the published preferred workflow just "edit your >>code in >> > www; cordova run <platform> to test", while still exposing the >>low-level >> > interface for developers who know what they're doing, and want control >> over >> > the prepare/compile/deploy cycle. >> > >> > Ian >> > >> > >> > On Wed, Jul 24, 2013 at 9:02 AM, David Kemp <[email protected]> wrote: >> > >> > > The run command in cli is documented (in help) as 'deploys an app'. >> > > The code in fact does a prepare, then deploy. >> > > >> > > This seems a little odd, since the normal cycle would be >> > > prepare,compile,deploy. >> > > Is this behavior intentional, or was this changed in error in >>CB-3460? >> > > >> > >>
