You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cordova.apache.org by "Filip Maj (JIRA)" <ji...@apache.org> on 2013/08/15 21:06:47 UTC

[jira] [Resolved] (CB-4591) Have hooks receive which platform the project command is executing for

     [ https://issues.apache.org/jira/browse/CB-4591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Filip Maj resolved CB-4591.
---------------------------

    Resolution: Duplicate

We've got this sort of filed as CB-4382, so I'll close this as a duplicate.

The idea in CB-4382 is that all parameter-type stuff would be passed to project-level hooks. Module-level (javascript) events get fired with a full data object containing all of this type of info (such as platforms), so we want to give the same data to project-level hooks.
                
> Have hooks receive which platform the project command is executing for
> ----------------------------------------------------------------------
>
>                 Key: CB-4591
>                 URL: https://issues.apache.org/jira/browse/CB-4591
>             Project: Apache Cordova
>          Issue Type: New Feature
>          Components: CLI
>    Affects Versions: 2.9.0
>         Environment: Cordova CLI 2.9.7
>            Reporter: Dan Moore
>            Assignee: Filip Maj
>            Priority: Minor
>
> Right now, project level hooks only get the base project directory as a parameter.  There are cases where it would be useful to know which platform the operation was taking place on.  (I did see a bug about module level hooks: https://issues.apache.org/jira/browse/CB-3929 but that doesn't seem to apply.)
> For instance, right now I'm trying to integrate flurry into my phonegap app.  I have different keys for my two platforms, and want to inject the correct key into my javascript via a hook.  
> There are no easy workarounds because hooks might be executed during 'cordova prepare' that might prepare two different platforms.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira