db.py: Refactor type annotations #1787
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more. @@ Coverage Diff @@
## master #1787 +/- ##
=======================================
Coverage 46.74% 46.75%
=======================================
Files 690 690
Lines 45701 45706 +5
=======================================
+ Hits 21365 21370 +5
Misses 24336 24336
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
RA80533
force-pushed
the
refactor/typing/spiderfoot--db
branch
from
3742694
to
3bf759a
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
scanResultEvent()'s arguments were not documented correctly. Many of them could belistin addition tostr.scanResultEvent()is not called correctly in several places (filterFpis often passed as the third arg).scanConfigSet()'sscan_idwas incorrectly documented as being anint(it's actually astr). It doesn't appear that this distinction matters to any of the places the function was called.