I wrote:
> Bryan Higgins wrote:
>> How does everyone feel about adding a warning message when the platform
>> version is older than CLI version?
>>
>> I've talked to some users recently who had no idea the update command
>> existed. They assumed that by updating via npm, their project would get
>>
Bryan Higgins wrote:
>How does everyone feel about adding a warning message when the platform
>version is older than CLI version?
>
>I've talked to some users recently who had no idea the update command
>existed. They assumed that by updating via npm, their project would get
>all
>of the bug fixes.
+1
On Mon, Dec 16, 2013 at 8:59 AM, Marcel Kinard wrote:
> Wondering if the "cordova info" command might also be a good place for
> this.
>
Wondering if the "cordova info" command might also be a good place for this.
+1, and I do think it should show up every time.
As long as it's just a one-line notice, doesn't appear if you run cordova
in quiet mode, and we don't design it to make the user feel like a bad
person for not updating, then I think it's useful to show on every run. If
nothing else, the user needs
Yep, that's not a bad plan:
Cordova updated to 3.x. To update your project platform scripts, run
'cordova platform update' from the project directory.
I was thinking of specifically calling out the platforms which need
updating on first run of cordova, but that would require us to keep track
of w
I wouldn't want to show the warning on every single command forevermore,
but definitely a good idea to slip it in there somewhere. Maybe we could
show it when they do an npm update?
On Mon, Dec 16, 2013 at 9:13 AM, Bryan Higgins wrote:
> How does everyone feel about adding a warning message when
How does everyone feel about adding a warning message when the platform
version is older than CLI version?
I've talked to some users recently who had no idea the update command
existed. They assumed that by updating via npm, their project would get all
of the bug fixes.
