On Thu, Jan 2, 2014 at 10:22 AM, Andrew Grieve <agri...@chromium.org> wrote:
> What cordova.json has that config.xml doesn't, is that you can set the > location of platforms with it through: > > > > That said, I like your idea of having one top-level config file instead of > two. I don't see why we couldn't just put these same settings into a > "cordova.xml". > Wouldn't this make it impossible to share project configuration between developers? If your /Users/agrieve/.../ paths are in your config xml, you're going to have a bad time putting that in version control. -1 on having a single file to manage both application config and build-environment config. +1 to the way I read Gorkem's original suggestion, which was to coordinate the move of the two files into a single issue and take care of it all at once. > > > On Wed, Jan 1, 2014 at 5:05 PM, Gorkem Ercan <gorkem.er...@gmail.com> > wrote: > > > There is also another proposal to move config.xml out of www. Can we > merge > > this two moves and > > 1. remove .cordova > > 2. remove config.json > > 3. move config.xml to root > > 4. rename config.xml to cordova.xml > > > > AFAIK config,json does not carry any information that is not already > > available on the config.xml. Since .cordova is basically a marker for CLI > > for the root of an app I think renaming config.xml should provide the > same > > functionality. > > -- > > Gorkem > > > > >
