Skip to content

feat(log): add Effect logger compatibility layer#17238

Draft
kitlangton wants to merge 2 commits intodevfrom
effect-log-compat
Draft

feat(log): add Effect logger compatibility layer#17238
kitlangton wants to merge 2 commits intodevfrom
effect-log-compat

Conversation

@kitlangton
Copy link
Contributor

Summary

  • add an effect-log compatibility layer that routes Effect logs through the existing util/log backend
  • preserve the current file and stderr logging behavior while forwarding Effect log levels, annotations, spans, and causes into legacy log metadata
  • add focused tests covering basic routing, annotations/spans forwarding, and structured message formatting

Add a small Effect logger bridge that routes Effect logs through the existing util/log backend so Effect-native services can adopt structured logging without changing the app's current file and stderr logging setup. Preserve level mapping and forward annotations, spans, and causes into the legacy logger metadata.
Replace the effect-log tests' global util/log module mock with local spies on Log.create so the logger compatibility tests no longer leak into unrelated unit suites. Keep the coverage for routing, annotations, spans, and cause formatting while allowing the full package test workflow to run cleanly.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant