This repository has been archived by the owner on Sep 20, 2024. It is now read-only.
General: Filter representations before integration start #3398
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.
Brief description
Representations filtering in
IntegrateAssetNew
happens as first step.Description
Representations were validated after subset and version creation and is not handled case when instance contains only representations that should not be integrated. Integration still fails if instance don't have any representations, but won't crash if none of those representations should not be integrated. Reset of
"transfers"
key on instance was moved to end of representations loop instead of at the start -> make sure that transfers end up with same values after each representation process.Testing notes:
Related to testing notes in PR