Talker Riverpod update: print full data for talker page #239
Conversation
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
|
Hello @yelmuratoff 🤝 |
|
@Frezyx is everything okay now?) |
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 #239 +/- ##
===========================================
+ Coverage 99.82% 100.00% +0.17%
===========================================
Files 28 3 -25
Lines 565 99 -466
===========================================
- Hits 564 99 -465
+ Misses 1 0 -1 ☔ View full report in Codecov by Sentry. |
Yes 💯 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Right now Riverpod Talker only displays full information for the console, but there is literally no information in the Talker Page itself. Not about the stats, not about the errors, stack trace.
I've changed the code to add more information, also added a new field for errors printFailFullData.