logd 0.4.1
logd: ^0.4.1 copied to clipboard
A professional, hierarchical logging library for Dart & Flutter. Features high-performance architecture, composable decorators, modular sinks, and thread-safe configuration.
Changelog #
0.4.1: Handler Robustness & Stability #
-
Critical Bug Fixes #
- FileSink Race Condition: Implemented mutex-based synchronization to serialize concurrent writes, preventing data loss during rapid logging
- TimeRotation Accuracy: Fixed timestamp tracking by updating
lastRotationafter successful writes, ensuring correct rotation triggers - Rotation Error Resilience: Enhanced error handling to continue writing to original file when rotation fails, preventing data loss
- BoxDecorator Width: Fixed internal content width calculation (
lineLength - 2) and added width clamping to prevent crashes - PlainFormatter Multi-line: Now joins multi-line messages to prevent format breaks in file logs
-
ANSI Code Handling #
- Added
wrapVisiblePreserveAnsi()to maintain ANSI styles across line breaks, fixing style loss in wrapped content - Added
padRightVisiblePreserveAnsi()to ensure padding inherits styling, preventing visual gaps in colored headers - Introduced
AnsiColorSchemeandAnsiColorConfigfor structured color customization - Replaced boolean
colorHeaderBackgroundwith explicitAnsiColorConfig(headerBackground: true)
- Added
-
Robustness & Idempotency #
- Width clamping in
StructuredFormatterandBoxDecoratorprevents negative width crashes BoxDecoratoridempotency check prevents nested box decorations- Fixed
LogBufferto avoid unnecessary stack trace creation during sink
- Width clamping in
-
Examples & Documentation #
- Added 17 comprehensive examples covering basic setups, formatters, decorators, sinks, filters, and edge cases
- Updated
docs/handler/README.mdwith color customization and edge case handling info - Added migration guide for
BoxFormatterand color configuration changes
-
Test Coverage #
- Added 13+ edge case test files validating concurrency, null handling, Unicode, ANSI codes, extreme widths, rotation timing, and error handling
- Over 2,400 new lines of test code ensuring robust behavior under edge conditions
0.4.0: Context-Aware Decorators & Visual Refinement #
-
Context-Aware Decoration Pipeline #
- Full Context Access:
LogDecorator.decorate()now accepts the fullLogEntryobject, granting decorators access to metadata likehierarchyDepth,tags, andloggerNamefor smarter transformations. - Automatic Composition Control: The
Handlerautomatically sorts decorators by type (Transform → Visual → Structural) to ensure correct visual composition, with deduplication to prevent redundant processing.
- Full Context Access:
-
Visual Refinements #
- Independent Coloring:
BoxDecoratornow supports its ownuseColorsparameter, allowing the structural border to be colored independently of the content.AnsiColorDecoratorcan now be focused purely on content styling. - Header Highlights:
AnsiColorDecoratoradds acolorHeaderBackgroundoption to apply bold background colors specifically to log headers, improving scannability in dense logs without bleeding into structural elements. - Hierarchy Visualization: Introduced
HierarchyDepthPrefixDecorator(formerly experimented asTreeDecorator). It adds visual indentation (defaulting to│) based on the logger's hierarchy depth, creating a clear tree-like structure in the terminal.
- Independent Coloring:
-
API & Robustness #
- Simplified BoxDecorator: Removed internal complexity from
BoxDecorator, making it a pureStructuralDecoratorfocused on layout. - Robustness Tests: Expanded test suite to cover deep decorator composition, ensuring that complex chains (Color -> Box -> Indent) render correctly without layout artifacts.
- Simplified BoxDecorator: Removed internal complexity from
0.3.1: Logger Architecture Refactor & Performance Optimization + Critical Bug Fix #
-
Bug Fix: Corrupted Pure Dart support fixed #
- Version 0.3.0 dropped support for pure dart due to a mis-used library. Fixed in version 0.3.1.
-
Architectural Shift: Separated Configuration from Resolution #
LoggerConfig&LoggerCache: Introduced a dual-component architecture for logger configuration.LoggerConfignow strictly holds raw, explicitly set configuration values, while the newLoggerCachehandles the hierarchical resolution (inheritance) and provides a high-performance caching layer.- Versioned Invalidation: Implemented a version-based cache invalidation mechanism.
LoggerConfigtracks changes via a_versioncounter, allowingLoggerCacheto lazily re-resolve effective settings only when the source configuration or its ancestry changes. - Thread-Safety & Immutability: Resolved configuration objects (like
handlersandstackMethodCount) are now returned as unmodifiable collections, protecting the internal state from accidental external mutation.
-
Performance: Deep Equality Optimization #
- Smart Reconfiguration:
Logger.configurenow performs deep equality checks on collections using internallistEqualsandmapEqualsutilities. This prevents redundant cache invalidations and descending tree walks when passing new collection instances that contain identical configurations. - Comprehensive Equality Support: Implemented
operator ==andhashCodeacross the entire configuration surface, including:- Handlers:
Handlernow correctly compares its formatter, sink, filters, and decorators. - Time Engine:
TimestampandTimezone(including DST rules and transition logic) now support value-based equality. - Stack Logic:
StackTraceParserandCallbackInfonow support deep comparison. - Filters & Formatters:
LevelFilter,RegexFilter,PlainFormatter,BoxFormatter, andJsonFormatterare now value-comparable.
- Handlers:
- Smart Reconfiguration:
-
Resilience & Testing #
- InternalLogger Resilience: Added targeted tests to verify that
InternalLoggerremains safe and circular-logging-free even when primary handlers fail, preventing stack overflows during failure recovery. - Deep Inheritance: Expanded the test suite to cover complex, multi-level hierarchy inheritance with partial overrides, ensuring configuration correctly "bubbles" through the tree.
- LogBuffer Integration: Verified the instance-based
LogBufferAPI (logger.infoBuffer) and its integration with the logging pipeline.
- InternalLogger Resilience: Added targeted tests to verify that
-
API & Maintenance #
- Immutability Enforcement: Applied
@immutableannotations to all core configuration and handler classes, providing better compile-time safety and alignment with modern Dart best practices. - Core Utilities: Centralized collection equality logic into
src/core/utils.dart.
- Immutability Enforcement: Applied
0.3.0: Robust Fallback Logging & Handler Resilience #
-
Fallback Logger for Circularity Prevention #
- Introduced
InternalLogger, a safe, direct-to-console logging mechanism for library-internal errors. - This prevents circular logging loops where a failure in a sink (like
FileSink) could trigger another error log, leading to infinite recursion. - Integrated
InternalLoggerintoLogger,FileSink,MultiSink,LogBuffer, andTimezone.
- Introduced
-
Improved Handler Resilience #
Loggernow catches errors from individual handlers. If one handler fails, it reports the error viaInternalLoggerand continues to process other handlers.MultiSinknow iterates through its sinks and handles individual sink failures independently, ensuring a single failing sink doesn't stop the entire output pipeline.
-
Bug Fixes & API Refinements #
- StackTraceParser: Fixed a regex bug that prevented parsing frames with spaces in method names, such as
<anonymous closure>. - API Visibility: Unhidden
LogEntryin the public API, as it is required for users to implement customLogFormatterinstances. - InternalLogger Visibility: Marked
InternalLoggeras@internalto keep it out of the public surface while still available for internal use.
- StackTraceParser: Fixed a regex bug that prevented parsing frames with spaces in method names, such as
0.2.3: Decoupled System Dependencies for Enhanced Testability #
-
Internal Service Locator for System Dependencies #
- Introduced an internal
Contextclass to act as a service locator for system-level dependencies likeClockandFileSystem. - This decouples the library from concrete implementations (e.g.,
DateTime.now(),dart:io), making it possible to inject mock implementations during testing. - Added
@visibleForTestingannotations to allow injecting customClockandFileSysteminstances in test environments. - This change significantly improves the testability and reliability of time-sensitive and file-system-dependent components.
- Introduced an internal
0.2.2: Enhanced FileSink Rotation & Custom Formatters #
-
Custom Filename Formatters for Rotated Logs #
SizeRotationandTimeRotationnow accept an optionalfilenameFormatterfunction.- This allows developers to define custom naming schemes for rotated log files, providing more control over backup organization.
-
Robust File Rotation & Cleanup Logic #
- The backup cleanup logic has been refactored to be more reliable. It now sorts backup files by their last modified timestamp to determine which to delete, instead of parsing potentially fragile filenames.
SizeRotationnow correctly renames the current log file to the first backup (e.g.,.1) before compression.
-
Improved Argument Validation & Reliability #
FileSinknow validates thebasePathto ensure it is not empty or a directory.FileRotationandTimeRotationconstructors now throw anArgumentErrorfor invalid arguments (e.g., negativebackupCount), replacing previousassertchecks.FileSink.write()now writes to the file withflush: trueto ensure data is immediately persisted.
0.2.1: Comprehensive Time Component Testing & Fixes #
-
Comprehensive Unit Testing #
Time&TimezoneTests: Addedtime_test.dartandtimezone_test.dartto verify mockable providers and extensive DST calculations across various rules and hemispheres.TimestampFormatter Tests: Addedtimestamp_test.dartto validate formatters, literal parsing, edge cases, and timezone handling.
-
Bug Fixes & Refinements #
- Timestamp Formatting: Corrected
iso8601andrfc2822formatters by removing extra single quotes to fix timezone literal rendering. The formatter token parser was also updated to correctly handle tokens containing underscores and digits. - DST Rules: Updated internal DST transition rules for several European timezones (
Europe/Paris,Europe/London,Europe/Berlin) to use the correct local transition times. - Time Class: Renamed
Time.resetTimeProvide()toTime.resetTimeProvider()for consistency. - Code Simplification: Replaced a manual Zeller’s congruence implementation for calculating the day of the week with a simpler call to
DateTime.utc().weekday.
- Timestamp Formatting: Corrected
0.2.0: Time Engine Overhaul & Mockable Time Provider #
-
Timestamp & Timezone Overhaul (Performance, DST, API) #
- Performance: Implemented a cached token system, eliminating the need to re-parse redundant formatters on every call.
- Mockable Time Provider: Introduced a mockable time provider (
Time.timeProvider) for robust testing of time-sensitive logic. TheTimeclass is now encapsulated with controlled access viasetTimeProvider()andresetTimeProvider(). - DST Support: Added full support for Daylight Saving Time (DST). The local timezone will resolve to a DST-aware timezone if available on the platform.
timezoneRenaming (Backward Incompatible): ThetimeZoneparameter was renamed totimezonefor consistency. TheTimeZoneclass was also renamed toTimezone.- DST Calculation Fix: Improved the DST offset calculation logic to better handle transitions.
- Platform Support: Enhanced platform-aware timezone detection, now including web support.
-
Advanced
TimestampFormatter #- Literal Support: The formatter now supports single-quoted literals (e.g.,
'on','at') to include static text in the output. - New Format Tokens:
'F...': For microseconds (for high-accuracy benchmarking).'E...': For weekdays (e.g., 'Monday').'a': For lowercase "am/pm".'z': For a standard-compliant timezone offset string (e.g.,Zor+0330).
- Token Changes: Removed the 'SSSS' token as it was redundant.
- Factory Constructors: Introduced common factory constructors like
Timestamp.iso8601(),rfc3339(),rfc2822(), andmillisecondsSinceEpoch().
- Literal Support: The formatter now supports single-quoted literals (e.g.,
-
Other Changes & Refinements #
- API Clarity: Renamed
LogBuffer.sync()toLogBuffer.sink(). - Improved Error Handling:
LogBufferandFileSinknow use the logger instance for error reporting instead ofprint(). - Code Refinements: Internal function and variable names related to timezones have been unified for better readability.
- API Clarity: Renamed
0.1.5: Async Logging / File Rotation #
-
Asynchronous Logging Pipeline #
- The entire logging pipeline, from
logger.log()tohandler.log()andsink.output(), is nowasync. - This prevents I/O operations (like file or network writes) from blocking the main thread.
- Error handling has been added to logging calls to catch and print exceptions that occur during the logging process itself.
- The entire logging pipeline, from
-
Advanced File Sink with Rotation #
- Introduced
FileRotationabstract class to enable log file rotation policies. - Added
SizeRotation: Rotates log files when they exceed a specified size (e.g., '10 MB'). - Added
TimeRotation: Rotates logs based on a time interval. - Both rotation policies support keeping a configured number of backup files and optional
gzipcompression for rotated logs.
- Introduced
-
Minor Refinements #
MultiSinknow outputs to all its sinks concurrently usingFuture.wait.- Added
//ignore: one_member_abstractstoLogFilterandLogFormatterto clean up analyzer warnings.
0.1.3: Pure Dart Support / Instantaneous Cached Configurations #
-
Pure Dart Optimizations #
- logd in now Dart ready. Decoupled from Flutter dependencies in favor of Dart standalone support.
-
Instantaneous Cached Configurations #
- Introduced
_LoggerConfig: Configuration is now stored in a separate internal_LoggerConfigclass, decoupling it from theLoggerinstance itself. This allowsLoggerto act as a lightweight proxy. - Improved Dynamic Hierarchy Propagation: Configuration changes now dynamically propagate down the logger tree.
- Cached Configuration: Resolved configuration values are now cached to improve performance by avoiding repeated hierarchy lookups. Caches are automatically cleared when parent configurations change.
- Simplified
configure(): Theconfigure()method now updates the configuration in-place rather than creating a newLoggerinstance. - Normalized Logger Names: Logger names are now consistently normalized to lowercase to ensure case-insensitivity. The root logger is consistently referred to as 'global'.
- Refactored
freezeInheritance(): ThefreezeInheritance()method has been updated to work with the new_LoggerConfigmodel, "baking" the current resolved configuration into descendant loggers. - Removed
attachToUncaughtErrors(): The method was removed from theLoggerclass.
- Introduced
-
TimeZone Improvements #
- The
Timestampconstructor'sformatterparameter is now required. - A new factory constructor,
Timestamp.none(), is introduced to create aTimestampwith an empty formatter. TimeZone.local()now correctly includes the system's current time zone offset.
- The
-
Improved FileSink (Still Under Development) #
- Automatically create parent directories for the log file path.
- Add more robust error handling:
- Rethrow exceptions in debug mode for easier debugging.
-
Comprehensive example demonstrating all
logdfeatures #
0.1.2: Minor API Changes #
0.1.1: Dynamic Logger Tree Hierarchy Inheritance #
-
Dynamic Inheritance #
- Logger tree is now dynamically propagated, rooting at 'global' logger
- freezeInheritance() is introduced to bake configs into a logger (and it's descendant branch, if any).
- global getter ditched in favor of uniformity: access global logger using get() or get('global').
0.1.0: Dot-separated Logger Tree Hierarchy + Handlers #
-
New Api #
- Logger has new Api surface.
- Introduced Dot-separated Logger Tree Hierarchy.
- Introduced functionalities to attach to Flutter/Dart Error and Unhandled Exceptions
-
Logger Tree Hierarchy #
- Loggers are named, now with a Dot-separated mechanism to inherit from their parent if not explicitly set. (Under Development)
- global Logger (still) available.
- Child propagation. (Under Development)
-
Handlers #
- Introduce Handlers: This Replaces Printers in V 0.0.2, no backward compatibility here!
- Introduced LogFormatters: Separated formatting LogEntries from outputting.
- Introduced LogSinks: Separated outputting LogEntries from formatting.
- Introduce LogFilters A way to filter out specific log entries.
-
Better Structure and Documentation #
0.0.2: Modularity + Printers #
-
Introduced Modular Loggers #
-
Introduced LogEvents #
-
Introduced Printers #
- Printers are a way of outputting data. (Soon to be replaced with Handlers: Formatters and Sinks)