Create list_container
as container
alternative for multiple objects with the same container path
#134
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.
Temporary workaround for #45 without breaking
container
compatibility before version 2SerializedFile
's_container
is also changed to be constructed using thelist_container
alternative so that all assets with a container path will properly show it instead ofNone
when accessed with.container
A
multiple_objects_per_container
flag is introduced toResourceManger.save()
andextract_assets()
inextractor.py
to utilizelist_container
with aFalse
default to avoid breaking compatibility