-
Notifications
You must be signed in to change notification settings - Fork 924
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(headertest): Validate exact error types in header tests #2644
feat(headertest): Validate exact error types in header tests #2644
Conversation
Codecov Report
@@ Coverage Diff @@
## main #2644 +/- ##
==========================================
+ Coverage 51.00% 51.14% +0.14%
==========================================
Files 158 158
Lines 10657 10657
==========================================
+ Hits 5436 5451 +15
+ Misses 4744 4731 -13
+ Partials 477 475 -2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for this <3
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't agree with this approach - we'd have nested error types with nested reasons. I don't think this is necessary nor good UX.
05de04c
to
08a9e9a
Compare
20a519f
to
e12581e
Compare
32c23b3
to
6cacfc6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a much neater diff now! Thanks
Co-authored-by: Hlib Kanunnikov <hlibwondertan@gmail.com>
2de5688
to
2b57bac
Compare
…aorg#2644) <!-- Please read and fill out this form before submitting your PR. Please make sure you have reviewed our contributors guide before submitting your first PR. --> ## Overview Closes: celestiaorg#2645 <!-- Please provide an explanation of the PR, including the appropriate context, background, goal, and rationale. If there is an issue with this information, please provide a tl;dr and link the issue. --> ## Checklist <!-- Please complete the checklist to ensure that the PR is ready to be reviewed. IMPORTANT: PRs should be left in Draft until the below checklist is completed. --> - [x] New and updated code has appropriate documentation - [x] New and updated code has new and/or updated testing - [ ] Required CI checks are passing - [ ] Visual proof for any user facing features like CLI or documentation updates - [x] Linked issues closed with keywords --------- Co-authored-by: Hlib Kanunnikov <hlibwondertan@gmail.com>
Overview
Closes: #2645
Checklist