-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
refactor: enhance error undefined message #5253
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 5d26428:
|
66b2ae7
to
98efbf3
Compare
98efbf3
to
8389312
Compare
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 5d26428. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this branch ✅ Successfully ran 4 targets
Sent with 💌 from NxCloud. |
you need to adapt the test that checks for this message please |
fixed 5d26428 |
Codecov ReportPatch coverage:
📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more Additional details and impacted files@@ Coverage Diff @@
## main #5253 +/- ##
==========================================
- Coverage 92.26% 91.78% -0.48%
==========================================
Files 112 101 -11
Lines 4267 3884 -383
Branches 1111 971 -140
==========================================
- Hits 3937 3565 -372
+ Misses 309 298 -11
Partials 21 21
... and 11 files with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
In production, it's hard to debug if got undefined data because error message don't tell which query is the problem.
To find the query or api, a developer should look many network logs. It's hard things and makes spend a lot of time.
when undefined error occurs production only, there is no clue which one is broken.
If throw "undefined" error with which query is the problem it makes easy to debug and save a lot of time.
Actually, this is from my experience. https://discord.com/channels/719702312431386674/1094894443447980152/1094894443447980152