You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Exciting stuff! 🎉 Things have certainly come a long way over this last year.
It doesn't look like logforth publicly depends on log, so I don't imagine you'd have any compatibility issues releasing a 1.0 of logforth based on the 0.4 version of log. We don't have any concrete stabilization plans there, but the last breaking release in log bent over backwards to maintain a single output target. This will also be an interesting use-case for us to consider if a breaking change does come about.
It doesn't look like logforth publicly depends on log
Currently, logforth directly depends on log::Record and log::Metadata, in Append and Layout and Filter interfaces.
But considering rust-lang/log#696 (comment), perhaps it's an alternative to have Logforth's own Record and Metadata alike type. Is it normal @KodrAus ?
* Rename `DefaultTrap` to `BestEffortTrap` for better clarity.
* Redesign `LevelFilter` to allow different comparison methods.
* Redesign `Level` as opentelemetry severity numbers.
* Add `Level::Fatal` variant to represent fatal level logs.
### New features
* Add `logforth-diagnostic-task-local` and `TaskLocalDiagnostic` to support task-local key-value context.
### Bug fixes
* Fix `FastraceDiagnostic` does not format `trace_id` and `span_id` as hex strings.
I'd expect some breaking changes in logforth-core to fine-tune the record APIs (Str, Metadata, Level, etc.) and consider once more about atexit cleanup (SpriteOvO/spdlog-rs#102 (comment)).
These changes may impact third-party components that depend on logforth-core, but the overall logforth experience, particularly for users who are primarily concerned with setup, should remain unchanged. Also, log is still our first-class facade.
That said, I'll review the starter experience frequently, so if you encounter any unexpected friction or have suggestions for improvement, just let me know!
Activity
KodrAus commentedon Aug 31, 2025
Exciting stuff! 🎉 Things have certainly come a long way over this last year.
It doesn't look like
logforthpublicly depends onlog, so I don't imagine you'd have any compatibility issues releasing a1.0oflogforthbased on the0.4version oflog. We don't have any concrete stabilization plans there, but the last breaking release inlogbent over backwards to maintain a single output target. This will also be an interesting use-case for us to consider if a breaking change does come about.tisonkun commentedon Sep 6, 2025
Currently,
logforthdirectly depends onlog::Recordandlog::Metadata, inAppendandLayoutandFilterinterfaces.But considering rust-lang/log#696 (comment), perhaps it's an alternative to have Logforth's own Record and Metadata alike type. Is it normal @KodrAus ?
tisonkun commentedon Oct 6, 2025
Almost done. Give it some time to review the API design.
The facade crate would keep in 0.x but all the core APIs and dedicated impls can go beyond 1.x.
tisonkun commentedon Oct 6, 2025
One last thing is to catch up on Level and LevelFilter API ideas:
nine9ths commentedon Oct 10, 2025
Do you anticipate any other breaking changes between 0.28 and 1.0? Trying to plan when we're going to do the upgrade from 0.27. Thanks!
tisonkun commentedon Oct 11, 2025
Cool! Here is an example of how our projects upgrade from 0.27 to 0.28:
Here is the current unreleased changelog:
logforth/CHANGELOG.md
Lines 5 to 21 in babe924
I'd expect some breaking changes in
logforth-coreto fine-tune the record APIs (Str, Metadata, Level, etc.) and consider once more about atexit cleanup (SpriteOvO/spdlog-rs#102 (comment)).These changes may impact third-party components that depend on
logforth-core, but the overalllogforthexperience, particularly for users who are primarily concerned with setup, should remain unchanged. Also,logis still our first-class facade.That said, I'll review the starter experience frequently, so if you encounter any unexpected friction or have suggestions for improvement, just let me know!
tisonkun commentedon Dec 18, 2025
Added #205 and #206 I hope the last thing comes to my mind before I can consider logforth core a 1.0 stable version.
env_filterto a dedicated crate #230