fix: resilient resolve logic of deep bindings [SPA-2110] #671
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.
Purpose
When an entry or asset was deleted which is used in a deep-bound value, the app would just crash in preview mode. Similarly to other places in the code, we want here also a less disrupting experience but just ignore broken bindings.
Approach
Similar to other cases covered in
gatherAutoFetchedReferentsFromIncludes
, we will create a debug message instead of throwing a crashing error.