-
Notifications
You must be signed in to change notification settings - Fork 8
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
Warnings tests #937
Warnings tests #937
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #937 +/- ##
==========================================
- Coverage 97.15% 97.12% -0.04%
==========================================
Files 23 23
Lines 10692 10709 +17
==========================================
+ Hits 10388 10401 +13
- Misses 304 308 +4
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
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.
Just a couple of questions, but basically looks good.
This PR adds a test that fails if warnings are emitted. We needn't enforce this check to pass on PRs, but it will warn us more clearly when there are deprecations etc.
I've fixed as many warnings as I could. This was quite a pain. I definitely recommend that someone with a bit more hera-cal knowledge go through and check that the warnings I'm silencing are appropriate. Sometimes I might be silencing something that shouldn't be.