Fix list insertion order and prevent runtime error in "Add After" feature #5767
Conversation
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
2 participants
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.
Description
This PR continues to address issue #5732.
🛠️ Fixes
Corrects the behavior of the "Add After" feature, which previously inserted new lists at the end instead of after the selected list.
Resolves a runtime error caused by a missing or undefined .list-position-input.
Ensures that ReactiveCache.getList is properly used and not replaced by non-reactive selection logic.
🧪 Manual Testing
Verified that adding a list "after" another correctly places it in the expected position.
Confirmed no JavaScript errors appear in the browser console.