Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Logging of upgrade messages - placement of some messages is incorrect #557

Closed
cpmcgrath opened this issue Jan 19, 2016 · 1 comment
Closed

Logging of upgrade messages - placement of some messages is incorrect #557

cpmcgrath opened this issue Jan 19, 2016 · 1 comment
Assignees
@ferventcoder
Labels
5 - Released Bug Priority_LOW Up For Grabs
Milestone
0.9.10

Comments

@cpmcgrath
Copy link

When you upgrade multiple items, the transition from one to the next looks like this...
chocoissue

This associates the yellow line with the first block of data. It of course has nothing to do with that block and everything to do with the next block.

A new line should be added before the yellow line, and preferably the new line after it removed.
@ferventcoder ferventcoder added this to the 0.9.10.x milestone Jan 19, 2016
@ferventcoder
Copy link
Member

Thanks for logging this!

eeevans added a commit to eeevans/choco that referenced this issue Jun 2, 2016
@eeevans
(chocolateyGH-557) Add newline preceding the newer version available …
6346a52 
…message.
eeevans added a commit to eeevans/choco that referenced this issue Jun 11, 2016
@eeevans
(chocolateyGH-557) Add newline preceding the newer version available …
fcfd994 
…message.
@ferventcoder ferventcoder self-assigned this Jun 11, 2016
@ferventcoder ferventcoder modified the milestones: 0.9.10, 0.9.10.x Jun 11, 2016
ferventcoder added a commit that referenced this issue Jun 11, 2016
@ferventcoder
(GH-557) Adjust logging of upgrade messages
7875987 
Upgrade messages should not look like they belong with the prior
package. Add a space before the message when logging to separate them
out.
ferventcoder added a commit that referenced this issue Jun 11, 2016
@ferventcoder
Merge branch 'stable'
69b4ec8 
* stable:
  (GH-715) Report loaded extension in debug
  (GH-455) Adjust summary for unfound sources
  (GH-557) Adjust logging of upgrade messages
  (GH-759) Summarize affected pkgs when at least 5
  (GH-759) One action summary for all actions
  (maint) rename method
  (GH-742) Feature List Formatting
  (maint) licensing updates
  (doc) update generated docs / add download
  (maint) Allow better use of PowershellService
  (GH-781) Web Functions - Return early when local file
  (doc) add more information regarding pro/business
  (GH-563) Environment changed message as warning
  (doc) Uninstall-ChocolateyZipPackage is optional
  (doc) Point to new docs location
  (maint) do not log warning unless regular output
  (GH-519) Update Install-ChocolateyShortcut Docs
  (doc) update generated docs
  (GH-773) Autodoc - Examples Before Parameters
  (GH-774) Autodoc - Fix Aliases
@ferventcoder ferventcoder changed the title Placement of the "You have {x} v{y} installed. Version {z} is available based on your source(s)' is wrong. Logging of upgrade messages - placement of some messages is incorrect Jun 11, 2016
@ferventcoder ferventcoder mentioned this issue Jun 13, 2016
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ferventcoder ferventcoder

Labels
5 - Released Bug Priority_LOW Up For Grabs
Projects
None yet
Milestone
0.9.10
Development

No branches or pull requests
3 participants
@ferventcoder @gep13 @cpmcgrath