Any chance we can start a conversation about simplifying this too? Passing
escaped JSON on the command line is, sorry, not a clean way to do this. As more
config options are added, this becomes less manageable.
On 3/26/2015 2:42 PM, Shazron wrote:
Whoever ends up fixing this, please add a test for the functionality
On Thu, Mar 26, 2015 at 11:35 AM, Josh Soref <[email protected]> wrote:
It's possible i broke it:
https://github.com/apache/cordova-cli/commit/106d8801a70a9b97cd606e27f80c6c7988f368cc#diff-ef7004c4000a2616f36c594dc5db207a
try something from before this?
i'd suggest a bisect
specifically, find the last version where the command worked;
then try only upgrading lib, to the version+1 and see if it worked, if so, it's
probably in cli.
i'd be really embarrassed if it's my fault.
i've been under the weather this week, so i'm catching up on mail/offering spot
advice and giving up.
________________________________________
From: Shazron [[email protected]]
Sent: Thursday, March 26, 2015 1:19 PM
To: [email protected]
Subject: Re: Setting config.json values
The help still says CONFIG is an option:
cordova create <PATH> [ID [NAME [CONFIG]]] [options] [PLATFORM...]
and config handling seems to still be there..
https://github.com/apache/cordova-lib/blob/cc596a37d77a92665292a5370d660a898217e0cb/cordova-lib/src/cordova/create.js#L41
.. so I think it's a bug. Two things here:
1. this bug
2. PLATFORM is not defined in the create help (I know it should be
obvious, but...)
On Thu, Mar 26, 2015 at 6:57 AM, John M. Wargo <[email protected]> wrote:
Earlier this month, there was a conversation on this thread about enabling
auto saving of plugin information to the project's config.json file
(.cordova/config.json, right?) by setting auto_save_plugins to true in the
file.
I responded on that thread suggesting that users would be able to set this
value by passing the configuration value on the command line to the cordova
create command like so:
cordova create test com.johnwargo.test Test
{\"auto_save_plugins\":\"true\"}
Shouldn't this be a viable way to enable users to automagically set this
value?
The problem is that this CLI feature no longer seems to work. Last fall, I
was able to set the plugin search path using the following:
cordova create test2 com.johnwargo.test2 Test2
"{\"plugin_search_path\":\"d:/dev\"}"
But I just tested it (for a second time on a different system) and that
capability, passing config.json values on the command line to create, no
longer seems to be working. Did I miss something? Was this feature removed?
Or should I submit a ticket on this issue?
Currently the SAP Mobile Platform Hybrid SDK ships as a local installer, the
plugins aren't in the plugin registry or even github. The plugins have local
dependencies (the AppUpdate plugin relies upon capabilities exposed by the
Logon plugin) and the Cordova CLI isn't able to resolve them locally without
the plugin_search_path being set. We've instructed users to use this
feature, but now it seems it's not working. Can someone confirm?
Since plugin_search_path is valuable for SAP customers and auto_save_plugins
is important for this new save/restore capability, is it time to design a
simpler approach to allow developers to easily set these properties as
needed for their projects? It seems that having a create command parameter
that points to a configuration file containing default settings for the
project would be a useful thing to have.
What says the group?
--
John M. Wargo
@johnwargo <http://twitter.com/johnwargo>
www.johnwargo.com <http://www.johnwargo.com>
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
