-
Notifications
You must be signed in to change notification settings - Fork 289
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
Fix for SerializableCollection::children_if #1404
Fix for SerializableCollection::children_if #1404
Conversation
Signed-off-by: Darby Johnston <[email protected]>
Signed-off-by: Darby Johnston <[email protected]>
Signed-off-by: Darby Johnston <[email protected]>
Signed-off-by: Darby Johnston <[email protected]>
Signed-off-by: Darby Johnston <[email protected]>
Signed-off-by: Darby Johnston <[email protected]>
Signed-off-by: Darby Johnston <[email protected]>
Signed-off-by: Darby Johnston <[email protected]>
Signed-off-by: Darby Johnston <[email protected]>
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #1404 +/- ##
==========================================
+ Coverage 85.99% 86.06% +0.07%
==========================================
Files 200 201 +1
Lines 20934 21062 +128
Branches 2459 2461 +2
==========================================
+ Hits 18002 18127 +125
- Misses 2331 2333 +2
- Partials 601 602 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
Signed-off-by: Darby Johnston <[email protected]>
I think I have addressed all the items from the issue as well as adding more consistent use of the "shallow_search" parameter to the various functions. @rogernelson has some interesting thoughts on a more efficient implementation of the "children_if" function, but maybe we need to decide whether the recursive searching functionality is actually appropriate for SerializableCollection. |
I think we should probably not do a major functionality switch on Thanks @darbyjohnston! I'll take a look at the code. |
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 good. Saw (maybe) a copy paste typo in the unit tests? I probably missed some but I might just be misunderstanding the use of assertTrue
, too. Let me know what you think!
Signed-off-by: Darby Johnston <[email protected]>
Signed-off-by: Darby Johnston <[email protected]>
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.
A few more assertTrue
still in there
Signed-off-by: Darby Johnston <[email protected]>
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.
Alright, this looks great. Thanks @darbyjohnston
…n#1404) * Fix for children_if * Missing shallow_search parameter fixes * Refactor test_children_if tests * Lint fixes * Add Python tests Signed-off-by: Darby Johnston <[email protected]> Signed-off-by: Michele Spina <[email protected]>
Signed-off-by: Darby Johnston [email protected]
Fixes #1400
Fixes an issue where SerializableCollection::children_if doesn't recurse into timelines. I'm marking this as a draft for now since it doesn't address all of the items in the issue (Python tests and missing arguments).