-
-
Notifications
You must be signed in to change notification settings - Fork 769
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
fix(2525): ensure non empty message when error of type string is passed, but no message #2544
fix(2525): ensure non empty message when error of type string is passed, but no message #2544
Conversation
…ing but no message
…to indicate sinon created the error
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #2544 +/- ##
==========================================
- Coverage 96.03% 95.95% -0.09%
==========================================
Files 40 40
Lines 1892 1904 +12
==========================================
+ Hits 1817 1827 +10
- Misses 75 77 +2
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
Just fix the Prettier thingie and this is good to merge :)
|
Done! |
Co-authored-by: Morgan Roderick <[email protected]>
Thank you for your contribution! 🥳 This has been published to the npm registry as part of |
Purpose (TL;DR) - mandatory
When an error of type String and an undefined message are passed to
throwsException
, ensure a non-empty error.messageSee issue: #2525
How to verify - mandatory
npm install
npm test
Checklist for author
npm run lint
passesNote: The branch currently causes this test to fail, so I'd appreciate guidance on whether expectations change, given this will result in a major semver change.