-
-
Couldn't load subscription status.
- Fork 101
[talker_riverpod_logger] add family arguments to the logs #377
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Reviewer's GuideThis PR enhances the Riverpod logger to append family-argument suffixes to provider log messages and adds corresponding tests verifying the new behavior. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @lucavenir - I've reviewed your changes and they look great!
Here's what I looked at during the review
- 🟡 General issues: 1 issue found
- 🟢 Security: all looks good
- 🟢 Testing: all looks good
- 🟢 Complexity: all looks good
- 🟢 Documentation: all looks good
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## master #377 +/- ##
===========================================
+ Coverage 98.61% 100.00% +1.38%
===========================================
Files 3 3
Lines 144 82 -62
===========================================
- Hits 142 82 -60
+ Misses 2 0 -2 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Changes description
Logging which provider of a family actually initialized, updated, disposed or failed is so much useful!
This helps both in development mode and in any analytics / crashlytics tools.
I noticed talker does a lot of effort to print provider base info, and forgets to print a provider's arguments.
That's why I chose to simply exploit riverpod's
provider.toString()- logging utilities in riverpod are ready made!(yes' I've added a test included ofc)
Summary by Sourcery
Enhance the riverpod logger to include family provider arguments in log messages across all provider lifecycle events.
New Features:
Enhancements:
Tests: