-
Notifications
You must be signed in to change notification settings - Fork 98
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
Adds limit for nested dict stats computation #421
Conversation
The CI issues have been fixed 🙏 Could you rebase/merge the latest changes from master? @mrwbarg |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #421 +/- ##
==========================================
+ Coverage 79.39% 79.42% +0.03%
==========================================
Files 76 76
Lines 3222 3228 +6
Branches 534 536 +2
==========================================
+ Hits 2558 2564 +6
Misses 593 593
Partials 71 71 ☔ View full report in Codecov by Sentry. |
@Gallaecio @rennerocha could you check on this PR? It's ready to be reviewed. |
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 is OK by me. However, I wonder if we should consider making the default -1 for no-limit, and make 0 cause this:
'spidermon_item_scraped_count/dict': 2
'spidermon_item_scraped_count/dict/field1': 2
'spidermon_item_scraped_count/dict/field2': 2
'spidermon_item_scraped_count/dict/field3': 1
'spidermon_item_scraped_count/dict/field4': 1
Can we close this in favor of #433 ? |
Closes #416
Adds a setting to limit how deep the coverage is computed for nested dicts.