Remove Library.all_collections
property.
#2191
Merged
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.
Description
Removes
Library.all_collections
(and its functionality), replaces its usage withLibrary.collections
, and removes a test assertion specific to this method.Motivation and Context
While working on PP-1875, I ran into this attribute, which provides a generator that yields both the collections associated with a library and the parents of those collections, where present.
It came in on this commit on this PR.
Here's some context from the PR description:
So, based on how we currently configure our collections that have parents -- specifically, we configure the library association for both OD main accounts and Advantage accounts, as appropriate -- I don't think we need the functionality it provides.
How Has This Been Tested?
Checklist