fix(frontend): handle multi-item array updates in updateYTypeFromObject#4265
Open
carloea2 wants to merge 1 commit intoapache:mainfrom
Open
fix(frontend): handle multi-item array updates in updateYTypeFromObject#4265carloea2 wants to merge 1 commit intoapache:mainfrom
carloea2 wants to merge 1 commit intoapache:mainfrom
Conversation
Contributor
Author
|
@chenlica @Xiao-zhen-Liu Thanks |
Contributor
Author
|
The new version has |
Contributor
|
@Xiao-zhen-Liu Please review it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What changes were proposed in this PR?
This PR fixes the pending TODO from
Arraybranch inupdateYTypeFromObject(...).texera/frontend/src/app/workspace/types/shared-editing.interface.ts
Lines 130 to 164 in ac909a0
Previously, the implementation assumed only one array update happened at a time and only handled the first mismatch with a single insert or delete. This caused incorrect behavior for multi-item insertions, multi-item deletions, and reorder cases.
This PR replaces that logic with an
Longest Common Subsequence based array diff so the finalY.Arraymatches the target array more reliably while still attempting in-place updates where possible.Any related issues, documentation, discussions?
Closes #4264
How was this PR tested?
Manually tested using:
Verified that the final
Y.Arraycontent matches the target array.Was this PR authored or co-authored using generative AI tooling?
Co-generated with GPT