Skip to content

Conversation

bjorkstromm
Copy link
Member

  • Expose ILoggingBuilder instead of accepting a ILoggerFactory

Some open questions. How to maintain backwards compatibility, or should we?

- Expose ILoggingBuilder instead of accepting a ILoggerFactory
@bjorkstromm bjorkstromm marked this pull request as ready for review October 7, 2019 20:55
@bjorkstromm
Copy link
Member Author

@david-driscoll is it worth it to work around and try to keep the old API with ILoggingFactory in order to don't break any existing users? We're still 0.x so might as well break 😄 Need to fixup the tests however, and probably fix the minimum loglevel also once for all 🛩

.WithOutput(process.ClientInputStream),
//.WithLoggerFactory(LoggerFactory)
//.AddDefaultLoggingProvider()
//.WithMinimumLogLevel(LogLevel.Trace),
Copy link
Member

Choose a reason for hiding this comment

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

Can probably safely delete these lines

.WithLoggerFactory(LoggerFactory)
.AddDefaultLoggingProvider()
.WithMinimumLogLevel(LogLevel.Trace)
//.WithLoggerFactory(LoggerFactory)
Copy link
Member

Choose a reason for hiding this comment

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

Can probably safely delete these lines

@david-driscoll david-driscoll changed the title Refactor logging Refactor logging +semver:minor Oct 10, 2019
@david-driscoll david-driscoll merged commit 2086370 into master Oct 12, 2019
@david-driscoll david-driscoll deleted the feature/refactor-logging branch June 2, 2020 04:47
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.

2 participants