Fix Flyde imports after file moves#265
Open
mdp28 wants to merge 1 commit into
Open
Conversation
mdp28
force-pushed
the
flyde-112-update-moved-imports
branch
from
ddd4be8 to
1f450c3
Compare
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
1 participant
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.
/claim #112
Summary
.flydefile-source imports after VS Code file/folder rename events..flyde.tsimports, legacy imports migrated bydeserializeFlow, inline visual nodes, and overlapping rename mappings.Verification
pnpm --filter flyde-vscode compile-testspassed locally before commit.node .\vscode\node_modules\mocha\bin\mocha.js --ui tdd .\vscode\out\test\flowFileReferences.test.jspassed locally: 10 passing.pnpm --filter flyde-vscode lintpassed locally before commit with existing unrelated warnings.Demo
The regression tests demonstrate the moved-import flows directly: moved imported flow, moved importing flow, simultaneous moves, folder moves, inline visual nodes, legacy imports, code-node imports, nested rename mappings, and sibling path safety.