This repository was archived by the owner on Apr 14, 2026. It is now read-only.
feat(logging): add Riverpod state observability via ProviderObserver (6/6)#245
Draft
feat(logging): add Riverpod state observability via ProviderObserver (6/6)#245
Conversation
…(6/6) Pipes all Riverpod provider state transitions into soliplex_logging at debug level. This gives LLMs (via get_app_logs) and integration tests (via TestLogHarness / MemorySink) full visibility into provider state changes — closing the last major observability gap. - Add LoggingProviderObserver (base class, Riverpod 3 API) - Add Loggers.state logger for State domain - Wire observer into ProviderScope in runSoliplexApp - Add unit tests verifying named and unnamed provider logging - Add worktree-safe wrapper scripts for pre-commit hooks
svarlet
approved these changes
Feb 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
LoggingProviderObserverthat pipes all Riverpod state transitions intosoliplex_loggingat debug levelLoggers.statelogger for theStatedomainProviderScopeinrunSoliplexAppChanges
base classimplementing Riverpod 3ProviderObserverAPI — logsprovider.name: newValueviaLoggers.state.debug()StateloggerLoggingProviderObserverintoProviderScope.observersdart formatandflutter analyzeWhy
Closes the last major observability gap: LLMs (via
get_app_logs) and integration tests (viaTestLogHarness/MemorySink) can now see all Riverpod state changes alongside HTTP traffic, auth events, and AG-UI lifecycle logs.Test plan
flutter analyze— 0 issues