You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cordova.apache.org by "Josh Soref (JIRA)" <ji...@apache.org> on 2014/03/24 20:20:50 UTC

[jira] [Commented] (CB-5782) Catch exceptions and print nice error when cordova-cli run from a non cordova project.

    [ https://issues.apache.org/jira/browse/CB-5782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13945562#comment-13945562 ] 

Josh Soref commented on CB-5782:
--------------------------------

1. I think that I want --verbose to include the stack CordovaError or not a CordovaError. Or possibly a --debug flag if people don't want --verbose for that purpose...
2. The change that reintroduced stacks has made downstream consumers less happy, so I'd like a --nostack flag (which our GUI will pass to cordova).
3. Is there a bug, plan, or schema for deciding which things should be CordovaErrors and which shouldn't be?

I posted a PR for the CLI side of 3 -- but that still leaves plugman at least.

> Catch exceptions and print nice error when cordova-cli run from a non cordova project.
> --------------------------------------------------------------------------------------
>
>                 Key: CB-5782
>                 URL: https://issues.apache.org/jira/browse/CB-5782
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: CLI
>            Reporter: Michal Mocny
>            Assignee: Mark Koudritsky
>            Priority: Minor
>
> cordova prepare prints scary stack trace when run from the wrong directory.  This is likely a common error and we should make it clear what is happening.
> Seems we are already catching the case, just failing to report it gracefully:
> throw new Error('Current working directory is not a Cordova-based



--
This message was sent by Atlassian JIRA
(v6.2#6252)