fix: reimplement removePartInstance
flow for syncChangesToPartInstances
#1410
+785
−199
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.
Note
This is a rebase of the PR for release53 of #1408
About the Contributor
This pull request is posted on behalf of the BBC
Type of Contribution
This is a: Bug fix
Current Behavior
This is a regression believed to be introduced by #1035
The
removePartInstance
method onSyncIngestUpdateToPartInstanceContext
is broken, it did not reset the PartInstance correctly.This PR reimplements this for the new model approach.
As part of this, some refactoring was done first, to make it easier to unit test portions of this logic. Not many tests have been added as part of this, but tests have been added for
removePartInstance
.I have not looked into backporting this fix to earlier releases, but I suspect it would be pretty straightforward to rebase it without the refactoring or unit tests.
Testing
Affected areas
Time Frame
Other Information
Status