CordovaError: why?

[Brian LeRoux <b...@brian.io>]

I saw the comment from/about StackOverflow but I am missing the point of
this. Any reason why we're doing this? (Eg reporting on a phone is weird,
etc.)

Otherwise, I feel this is a loss of clarity for cleverness and would opt to
remove (slowly) since its everywhere in the code.

Re: CordovaError: why?

[Mark Koudritsky <ka...@google.com>]

Not sure I understood the question, but this bug has the history of
CordovaError
https://issues.apache.org/jira/browse/CB-5782

In short, it was added to allow printing full stack trace for unexpected
errors, but only print the short message for _some_ of the errors we throw
ourselves, mostly the errors that result from bad user input such as a typo
in platform name or running from a dir which is not a cordova project.


On Tue, May 20, 2014 at 12:33 AM, purplecabbage <pu...@gmail.com>wrote:

> Totally missing the context here. Did you mean to link to stack overflow?
>
> Sent from my iPhone
>
> > On May 19, 2014, at 3:11 PM, Brian LeRoux <b...@brian.io> wrote:
> >
> > I saw the comment from/about StackOverflow but I am missing the point of
> > this. Any reason why we're doing this? (Eg reporting on a phone is weird,
> > etc.)
> >
> > Otherwise, I feel this is a loss of clarity for cleverness and would opt
> to
> > remove (slowly) since its everywhere in the code.
>

Re: CordovaError: why?

[purplecabbage <pu...@gmail.com>]

Totally missing the context here. Did you mean to link to stack overflow?

Sent from my iPhone

> On May 19, 2014, at 3:11 PM, Brian LeRoux <b...@brian.io> wrote:
> 
> I saw the comment from/about StackOverflow but I am missing the point of
> this. Any reason why we're doing this? (Eg reporting on a phone is weird,
> etc.)
> 
> Otherwise, I feel this is a loss of clarity for cleverness and would opt to
> remove (slowly) since its everywhere in the code.