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

[editorial] Remove implementation detail from Logs Bridge API #3884

Merged
merged 5 commits into from
Feb 28, 2024
Merged

[editorial] Remove implementation detail from Logs Bridge API #3884

Changes from 2 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
40f88ef
Remove implementation detail from Logs Bridge API
MrAlias Feb 16, 2024
83a0539
Merge branch 'main' into rm-stateful-log
MrAlias Feb 20, 2024
d47bf0c
Add changelog entry
MrAlias Feb 20, 2024
b58f318
Merge branch 'main' into rm-stateful-log
MrAlias Feb 23, 2024
c4338fc
Merge branch 'main' into rm-stateful-log
MrAlias Feb 27, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 0 additions & 3 deletions specification/logs/bridge-api.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,9 +46,6 @@ graph TD

`Logger`s can be accessed with a `LoggerProvider`.

In implementations of the API, the `LoggerProvider` is expected to be the stateful
MrAlias marked this conversation as resolved.
Show resolved Hide resolved
object that holds any configuration.

Normally, the `LoggerProvider` is expected to be accessed from a central place.
Thus, the API SHOULD provide a way to set/register and access a global default
`LoggerProvider`.
Expand Down
Loading