Skip to content
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

feat: allow overriding name property #59

Merged
merged 1 commit into from
Aug 6, 2024
Merged

Conversation

achingbrain
Copy link
Owner

Adds an errorName option that allows overriding the .name property of the thrown error.

Adds an `errorName` option that allows overriding the `.name`
property of the thrown error.
Copy link

codecov bot commented Aug 6, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (2067ab6) to head (f0c8b6c).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #59   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            2         2           
  Lines          143       149    +6     
  Branches        32        33    +1     
=========================================
+ Hits           143       149    +6     
Flag Coverage Δ
chrome 100.00% <100.00%> (ø)
node 100.00% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@achingbrain achingbrain merged commit c9f8798 into main Aug 6, 2024
20 checks passed
@achingbrain achingbrain deleted the feat/override-error-name branch August 6, 2024 18:41
github-actions bot pushed a commit that referenced this pull request Aug 6, 2024
## [1.1.0](v1.0.3...v1.1.0) (2024-08-06)

### Features

* allow overriding name property ([#59](#59)) ([c9f8798](c9f8798))
Copy link

github-actions bot commented Aug 6, 2024

🎉 This issue has been resolved in version 1.1.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant