Change console color for updated packages

[forki]

@agross suggested we should change the console color to green when paket update changes the version of a package.

<green>nanoc 4.2.3 (was 4.2.1)</green>

[forki]

I think this should be pretty easy if one pipes the lockfile through the corresponding functions.

[TeaDrivenDev]

I've been trying to figure out what would be necessary here, but I can't find where something needs to be done. Is it correct that the "(was x.x.x)" part doesn't exist yet?

[forki]

Yes that doesn't exist

Am 15.08.2016 4:30 nachm. schrieb "TeaDrivenDev" notifications@github.com:

I've been trying to figure out what would be necessary here, but I can't
find where something needs to be done. Is it correct that the "(was x.x.x)"
part doesn't exist yet?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#1801 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADgNCm76sqv1LRtImqwO2zPhbV4F2Ikks5qgHgXgaJpZM4JKVDt
.

[TeaDrivenDev]

So.... This is the full output of paket update for a single package:

Paket version 3.13.0.0
Resolving packages for group Main:
- AutoFixture 3.50.1
Locked version resolution written to D:\Development\Test\PaketTest\paket.lock
Downloading AutoFixture 3.50.1
4 seconds - ready.

Where would this information go? In the - AutoFixture 3.50.1 line, or as a new line after Downloading AutoFixture 3.50.1?

[forki]

I would put it at the bottom. Just like a summary of what happened

Am 15.08.2016 16:52 schrieb "TeaDrivenDev" notifications@github.com:

So.... This is the full output of paket update for a single package:

Paket version 3.13.0.0
Resolving packages for group Main:

• AutoFixture 3.50.1
  Locked version resolution written to D:\Development\Test\PaketTest\paket.lock
  Downloading AutoFixture 3.50.1
  4 seconds - ready.

Where would this information go? In the - AutoFixture 3.50.1 line, or as
a new line after Downloading AutoFixture 3.50.1?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#1801 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADgND18VDcW756nzwc168Ty19EqbmtLks5qgH0ggaJpZM4JKVDt
.

[agross]

The bottom is great. Bundler puts these inline, so it's hard to find them. I think this is because in case of an error the abnormal exit would not print any of the update information.

[forki]

npm puts a report at the bottom...

2016-08-15 17:05 GMT+02:00 Alexander Groß notifications@github.com:

The bottom is great. Bundler puts these inline, so it's hard to find them.
I think this is because in case of an error the abnormal exit would not
print any of the update information.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#1801 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADgNBT3LWjKr1tU2bKTNc1BexRhJRdsks5qgIAxgaJpZM4JKVDt
.