Skip to content

fix(vscode): update relative node imports when moving or renaming files - #298

Open
sonofkratos92 wants to merge 1 commit into
flydelabs:mainfrom
sonofkratos92:fix-broken-imports-on-move-112
Open

sonofkratos92 wants to merge 1 commit into
flydelabs:mainfrom
sonofkratos92:fix-broken-imports-on-move-112

Conversation

@sonofkratos92

Copy link
Copy Markdown

Summary

Fixes broken relative imports when moving or renaming files in the VS Code extension:

  • Adds registerFileMoveImportUpdater (vscode/src/updateImportsOnMove.ts) hooked into vscode.workspace.onDidRenameFiles.
  • Recomputes relative paths for file-sourced node instances (source.type === "file", including nested inline visual nodes) and legacy imports maps when:
    • an imported .flyde.ts / .flyde.js code node or .flyde visual subflow is moved or renamed,
    • a .flyde flow file itself is moved to a different folder, or
    • a parent directory is moved/renamed.
  • Applies updates via vscode.WorkspaceEdit so open Flyde editor panels automatically receive the updated flow.
  • Adds unit tests in vscode/src/test/updateImportsOnMove.spec.ts.

Fixes #112
/claim #112

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Broken imports after moving files

1 participant