Skip to content

Conversation

@grouma
Copy link
Member

@grouma grouma commented Apr 19, 2019

This assumes the logger names do not contain spaces. Based off of dart-lang/build#2194 this assumption appears correct.

Closes #301

@grouma grouma requested a review from jakemac53 April 19, 2019 16:36
Copy link
Contributor

@jakemac53 jakemac53 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is deserving of some specific unit tests to cover some of the potential edge cases (multiple colons, colons in the log message but no actual logger name provided, empty log message with a logger name, etc)

@grouma grouma merged commit 750f6a6 into master Apr 22, 2019
@grouma grouma deleted the log-names branch April 22, 2019 16:30
natebosch added a commit to dart-lang/build that referenced this pull request Apr 22, 2019
Now that there is a split with some of these logger names coming from
`build_runner_core` it's not as easy to roll out changes which introduce
new logger names. The only cases where we do want to show the logger
name are the ones where we are running actions and will always fit the
pattern of `'$builderLabel on $input'`.

`wevdev` parses out logger names and discards any which contain a
space:
dart-lang/webdev#305
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

serve command is printing logger names

3 participants