Skip to content

Conversation

@bnjjj
Copy link
Contributor

@bnjjj bnjjj commented Apr 4, 2020

Motivation

close #653

…rs#653

Signed-off-by: Benjamin Coenen <5719034+bnjjj@users.noreply.github.com>
Copy link
Member

@hawkw hawkw left a comment

Choose a reason for hiding this comment

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

Thanks for the PR! Because this is a breaking change, it won't merge until we're ready to release an 0.3 version of tracing-subscriber. However, it's very helpful to have this ready to go.

Would you mind also giving the docs a quick skim to make sure we don't state that the json feature is on by default? Thanks.

@bnjjj
Copy link
Contributor Author

bnjjj commented Apr 10, 2020

It will be done this weekend :)

@bnjjj
Copy link
Contributor Author

bnjjj commented Apr 12, 2020

After checking the documentation it seems nothing has to be updated

@hawkw hawkw added this to the tracing-subscriber 0.3 milestone Jul 8, 2020
@bnjjj bnjjj requested a review from a team as a code owner August 5, 2020 03:08
@hawkw hawkw changed the base branch from master to subscriber-0.3-dev August 6, 2020 22:08
@hawkw
Copy link
Member

hawkw commented Aug 6, 2020

I've changed the base branch for this PR to the tracing-subscriber v0.3 dev branch.

@hawkw hawkw merged commit 5535b2b into tokio-rs:subscriber-0.3-dev Nov 21, 2020
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.

Remove json support from tracing-subscriber's default features

2 participants