-
Notifications
You must be signed in to change notification settings - Fork 72
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.
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
User-configurable synchronized writes #66
Conversation
enabling scenarios where the application needs to sync with the console, or the application wants to keep multiple console sinks which do not need to be sync'd.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should bump the major version for this, although the (binary API) breakage will be minimal.
Before merging (with the bumped major) we also should make sure any minor revision changes sitting on dev are merged to master and released.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great! I think this is good to go. I'll check on the state of dev
and increment the major version number before merging.
🎉 |
This is great, exactly what I was looking for. Any idea when this might be merged to master? |
#82 is tracking this |
What issue does this PR address?
#65
Does this PR introduce a breaking change?
Yes, it's a breaking change. We could make it non-breaking (and I did originally), but it's feels like it might not be worth it. Adding overloads with a new required parameter
syncRoot
just for this seems a little too much.Please check if the PR fulfills these requirements
Wit the sample you can:
dotnet run -- --sync-root-separate
which will produce garbled output:dotnet run -- --sync-root-same
which produce properly sync'd output:dotnet run -- --sync-root-default
which will not configure thesyncRoot
(leaving the default as per #65: