✅ Provide cause when doc generation fails#6472
Conversation
Until now when the generation of the doc was failing we just received an error telling us about the snippet that failed to execute. Now that Node supports errors coming with causes, we can leverage them to have a more understandable error.
|
@fast-check/ava
@fast-check/expect-type
fast-check
@fast-check/jest
@fast-check/packaged
@fast-check/poisoning
@fast-check/vitest
@fast-check/worker
commit: |
|
👋 A preview of the new documentation is available at: http://69710cc48ab06b52a95ef2ee--dubzzz-fast-check.netlify.app |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #6472 +/- ##
=======================================
Coverage 94.85% 94.85%
=======================================
Files 207 207
Lines 5581 5581
Branches 1467 1467
=======================================
Hits 5294 5294
Misses 274 274
Partials 13 13
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Description
Until now when the generation of the doc was failing we just received an error telling us about the snippet that failed to execute. Now that Node supports errors coming with causes, we can leverage them to have a more understandable error.
Checklist — Don't delete this checklist and make sure you do the following before opening the PR
pnpm run bumpand flag the impacts properlyAdvanced