-
Notifications
You must be signed in to change notification settings - Fork 377
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
Upgrade steep and make it a bit more strict #4221
Conversation
Datadog ReportBranch report: ✅ 0 Failed, 22094 Passed, 1457 Skipped, 5m 16.97s Total Time |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #4221 +/- ##
=======================================
Coverage 97.75% 97.75%
=======================================
Files 1355 1355
Lines 82165 82163 -2
Branches 4207 4207
=======================================
- Hits 80321 80320 -1
+ Misses 1844 1843 -1 ☔ 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.
👍
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 think my suggestions are non-blocking, but gems versions are kind-a important
Co-authored-by: Sergey Fedorov <[email protected]>
Upgrade steep to
1.9.1
and rbs to3.7.0
, as I've encountered recent steep bugs that have been fixed in newer versions.I also played a bit with the default type checking level: we currently use
default
but I've triedstrict
and noticed there are a few very helpful checks.Most notably:
DifferentMethodParameterKind
which checks that your.rbs
declarations actually match the method parameters.IncompatibleAssignment
which checks if we are assigning incompatible types to fields we've explicitly typed already.There's one functional change which steep caught in this upgrade: there was one dead code branch in
lib/datadog/appsec/processor/rule_loader.rb
, which I removed. This is actually dead code, sinceip_passlist
comes from a non-nillable configuration option.Change log entry
None