Show more precise debugging steps #286
Draft
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
Codecov Report
@@ Coverage Diff @@
## main #286 +/- ##
==========================================
+ Coverage 22.91% 23.32% +0.41%
==========================================
Files 9 9
Lines 371 373 +2
==========================================
+ Hits 85 87 +2
Misses 286 286
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
Member
|
Nice, that's a great idea! |
Member
|
Love it! Having a precise error message will be really helpful, both for the users and for us. |
Contributor
|
For the last part, can we also direct them to include the function call and not only the error text (is that accessible from the error object we are printing?)? I don't know that just getting |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is related to #283. It is not at all complete, I just did a small test on the "Assumption checks" part to see how to customize the error message to give more precise steps. I implemented an error manually (
log("a")) just to simulate an error.Here's the current output:
And here's the new type of error messages:
@easystats/core-team What do you think? Should it be generalized to the other parts of the dashboard?