Skip to content

Conversation

pblazej
Copy link
Contributor

@pblazej pblazej commented Oct 9, 2025

Turns out that the configuration closure:

  • must be run before any logs (expected) - this is kinda fixable
  • may run once per process, so will break for anyone using the same framework... and we cannot do any default setup

If we need the flexibility anyway, maybe it's better to drop the swift-logging right now...

My assupmtions:

  • we use pure OSLog by default (info or warning)
  • we can easily enable rtc internal logs via the same channel
  • we can easily provide our custom implementation

Copy link

github-actions bot commented Oct 9, 2025

⚠️ This PR does not contain any files in the .changes directory.

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.

1 participant