debug_kit_riverpod 0.5.0
debug_kit_riverpod: ^0.5.0 copied to clipboard
Riverpod provider observer adapter for DebugKit. Records provider state events into the State tab with sanitization and optional log mirroring.
Changelog #
0.5.0 #
Added #
- Added structured Riverpod value serialization for
AsyncValue,toJson(),toMap(), iterables, and custom serializer output.
Changed #
- Updated the adapter to support
debug_kit ^0.11.0. - Improved provider previews so complex models no longer collapse to
Instance of ...when structured data is available.
0.4.0 #
Added #
- Added State tab integration for Riverpod provider lifecycle events.
Changed #
- Routed Riverpod provider lifecycle events into DebugKit's dedicated State tab by default.
- Stopped flooding the main Logs tab with provider updates unless
mirrorStateChangesToLogsis enabled. - Improved provider name resolution so explicit names are preferred, readable provider-derived fallbacks are used when possible, and
UnnamedProvideris reserved for true last-resort cases. - Structured provider updates now include changed paths for JSON-like
Map/Liststate where possible. - Added
recordProviderAdds,recordProviderUpdates,recordProviderDisposals,recordProviderErrors,mirrorStateChangesToLogs, andmirrorErrorsToLogsconfiguration options. - Updated the package to support
debug_kit ^0.10.0.
Notes #
logProviderUpdatesremains as a deprecated compatibility alias forrecordProviderUpdates.- Provider failures still mirror into Logs by default so errors remain visible.
- Provider values are sanitized and truncated before they reach the State tab.
- Arbitrary Dart objects fall back to sanitized previews when a structured diff is not available.
- The State tab keeps source metadata in event details, but it does not expose a single-source filter in the toolbar.
0.3.0 #
Added #
- Added support for Riverpod 3 projects.
Changed #
- Updated the adapter to support
debug_kit ^0.9.0. - Migrated observer integration to the Riverpod 3
ProviderObserverAPI. - Kept Riverpod logs flowing through DebugKit core so in-app logs and sanitized console mirroring share the same pipeline.
Notes #
- Riverpod 3 users should use
debug_kit_riverpod ^0.3.0. - Riverpod 2 users should stay on
debug_kit_riverpod ^0.2.3. - This release does not support Riverpod 2.
0.2.3 #
Changed #
- Updated the Riverpod 2 adapter line to support
debug_kit ^0.9.0. - Kept compatibility with Riverpod 2
ProviderObserverAPIs. - Kept Riverpod logs flowing through DebugKit core so in-app logs and sanitized console mirroring share the same pipeline.
Notes #
- Riverpod 2 users should use
debug_kit_riverpod ^0.2.3. - Riverpod 3 support will be introduced separately in
debug_kit_riverpod 0.3.0.
0.2.2 #
- fix: widen
flutter_riverpodconstraint to">=2.0.0 <4.0.0"(was^2.0.0) to allow apps using Riverpod 3.x. - chore: update
repositoryandissue_trackerURLs to reflect repository rename. - No runtime behavior changes.
ProviderObserver.providerDidFailanddidUpdateProviderare unchanged in Riverpod 3. - No API changes.
0.2.1 #
- Fix: add
TestWidgetsFlutterBinding.ensureInitialized()to the test suite so trace store event tests pass reliably when the Flutter scheduler binding is required. - Bump minimum
debug_kitconstraint to^0.5.0to align with the Error Digest release. - Update README install snippet to current versions.
0.2.0 #
- Trace correlation: Provider failures that occur inside an active
DebugKit.trace.run()zone now automatically carrytraceIdandtraceNameon the log entry. - State trace events: A
statetrace event is recorded on the active trace when a provider fails inside a trace. - No behavior change when no trace is active — all existing logging behavior is preserved.
0.1.0 #
- Initial release of
debug_kit_riverpod. - Added
DebugKitRiverpodObserverto log provider failures and optional state updates. - Added
DebugKitRiverpodConfigto manage log behavior and verbosity safely. - Included security sanitization to mask obvious secrets in value previews.