Skip to content

fix: resolve and update relative file imports after moving files (#112) - #296

Open
Aldii24 wants to merge 2 commits into
flydelabs:mainfrom
Aldii24:fix/broken-imports-after-moving-files
Open

Aldii24 wants to merge 2 commits into
flydelabs:mainfrom
Aldii24:fix/broken-imports-after-moving-files

Conversation

@Aldii24

@Aldii24 Aldii24 commented Oct 26, 2026 •

Copy link
Copy Markdown

Fixes #112
/claim #112

Updates relative file imports when .flyde flows, code nodes, or folders are moved:

  • Rewrites relative source: { type: "file", data } paths (including nested inline visual nodes) and legacy imports entries via vscode.workspace.onWillRenameFiles.
  • Rebases relative file sources inside imported visual subflows (rebaseVisualNodeFileSources) and resolves editorComponentBundlePath relative to the code node's own directory first.
  • Falls back to locating moved node files by filename and nodeId (resolveMovedFilePath) when a relative import path was moved outside VS Code.
  • Adds unit tests in loader/src/resolver/movedFileImports.spec.ts.

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