-
Notifications
You must be signed in to change notification settings - Fork 123
Allow more configuration with Catalog.validate_all
#1141
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
Conversation
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #1141 +/- ##
==========================================
+ Coverage 91.17% 91.18% +0.01%
==========================================
Files 49 49
Lines 6626 6634 +8
Branches 978 980 +2
==========================================
+ Hits 6041 6049 +8
Misses 410 410
Partials 175 175
☔ 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.
Looks great. PR approved, but question as to if it closes 1141
Between the attempt to skip CI and the force push I broke this PR 🤦 Opening a new one now |
Related Issue(s):
Description:
I think this covers the scenario described in the original issue of limiting the amount of objects that are iterated over. It made more sense to be to track that as a single number (items + catalogs + collections) and then to separately give a knob for changing whether or no we recurse into the children.
That being said there are lots of ways to tackle this. Anther approach could use a timeout rather than tracking number of objects at all.
PR Checklist:
pre-commit
hooks pass locallyscripts/test
)