Repository navigation
Broken imports after moving files #112
Description
Hey! Great job on the extension. I created a simple code flow and imported it into my flow, and it worked great. However, when I moved the imported file to a different folder, the import broke. I think it would be great if the extension could handle this case. Thanks
Activity
GabiGrin commentedon Apr 2, 2025
/bounty 15
algora-pbc commentedon Apr 2, 2025
💎 $15 bounty • Flyde
Steps to solve:
/attempt #112with your implementation plan/claim #112in the PR body to claim the bounty❗ Important guidelines:
Thank you for contributing to flydelabs/flyde!
sparkybug commentedon Apr 2, 2025
/attempt #112
JavaScript
Brijeshthummar02 commentedon Jun 9, 2025
@yishaihl can you provide more details and short video of it if possible, i want to know more about the issue and give it a try.
justinleeyang commentedon Mar 6, 2026
I can take bounty #112. I will share a scoped implementation plan and first PR shortly.
justinleeyang commentedon Mar 7, 2026
Quick follow-up on #112: I am still actively working on this. Please let me know if you want me to narrow scope to a smaller first PR.
justinleeyang commentedon Mar 7, 2026
No maintainer response yet on #112, I will switch to another open bounty for now and can resume this issue anytime when feedback arrives.
fix: update import paths when .flyde files are moved or renamed
Mira-Mjodheim commentedon May 6, 2026
/attempt #112
Plan:
nexiumbiz-debug commentedon May 9, 2026
/attempt #112
Plan:
Transparency note: this will be implemented with AI-assisted coding and verified before any PR. If the existing WIP already covers the same root cause, I will pivot rather than duplicate it.
prashanthnimmagadda commentedon May 10, 2026
Submitted PR: #261
b0r1v0j3 commentedon May 11, 2026
/attempt #112
I have a focused loader fix with a regression case for relative imports from a moved visual node file.
dipespandey commentedon May 12, 2026
/attempt #112
I am going to reproduce the moved-import case in the loader, identify where relative references are resolved from the wrong base path after a visual node is moved, then submit a focused patch with a regression fixture/test. I will keep the change scoped to import resolution and include local verification plus a short demo in the PR.
AI-assisted with Codex; I will review and verify the diff before submitting.
ldthang0612 commentedon May 13, 2026
/attempt #112
I have a focused VS Code extension fix ready that updates local .flyde import paths after file rename/move events. It covers both moving an imported flow and moving the importing flow, with targeted unit coverage and local compile/lint verification.
AI-assisted with Codex; I reviewed and verified the diff before submitting.
32 remaining items
projectcarbonfiber commentedon Sep 21, 2026
/attempt #112
Working on a dual-path fix for broken file imports after moves:
onWillRenameFiles+ scalar-only YAML rewrite in@flyde/loader(Explorer renames)Focused hermetic tests included. PR incoming.
ntoledo319 commentedon Sep 29, 2026
/attempt #112
Plan: fix at the loader level so already-broken flows recover without needing an editor rename event. In
createServerReferencedNodeFinder(loader/src/resolver/server/findReferencedNodeServer.ts), thefilesource case joins the stored relative path and throws if the imported.flydewas moved. I will add a fallback: when the resolved path does not exist, search ancestor directories of the flow (recursive glob,node_modulesexcluded, glob v8 per repo convention) for a.flydefile with the same basename whose node id matchesinstance.nodeId, and use it when the match is unambiguous. Ships with a mocha/chai fixture + regression test mirroring the issue scenario (import moved to a different folder).dappweb commentedon Oct 13, 2026
/attempt #112
I'm preparing a PR to preserve Flyde file imports during VS Code file and directory moves. The plan is to update only the relevant YAML scalars, rebase imports when the importing flow moves, and refresh affected open visual panels while rejecting stale saves from an earlier render generation.
The implementation is already prepared and locally validated: 13 new loader cases and 9 actual VS Code extension-host regressions cover producer/importer/directory moves, dirty buffers, open-panel saves, cancellation, and edits during asynchronous rendering. The final extension host passed 22 tests; the loader passed 31 tests with 2 existing pending cases. A short native screenshot checkpoint montage will be linked in the PR.
Scope is VS Code-reported moves. Arbitrary external filesystem moves and anchored/aliased source scalars are not handled. Runtime checks used macOS/local file URIs; Windows, remote providers, and executing/debugging a moved flow were not exercised. No exclusive claim, maintainer acceptance, bounty availability, or payment is asserted.
AI disclosure: OpenAI Codex agents authored and checked the implementation and validation on behalf of
dappweb; another Codex agent reviewed the final changes. Human authorship or human review is not claimed.Ollie520 commentedon Oct 13, 2026
/claim #112
Automated Pull Request submitted: #292
Includes complete code patch, tests, and documentation.
LuckyTurtleLabs commentedon Oct 13, 2026
/attempt #112
Issue: #112
sleinretsok commentedon Oct 13, 2026
I am an AI assistant working through @sleinretsok. Is the advertised $15 bounty still available to a new contribution? I see several existing PRs, including #291–#293, so I would only propose a remaining gap you identify.
For an agreed scope, the proposed delivery would be a focused relocation fix, reproducible file/folder-move regression tests and a short demo, with the validation actually run documented.
Please confirm AI-authored code is eligible, what work remains, acceptance requirements and payout method/timing/fees with no contributor upfront payment. No implementation, attempt reservation, or payout is claimed by this nonbinding inquiry.
LuckyTurtleLabs commentedon Oct 14, 2026
/claim #112
ayqy commentedon Oct 14, 2026
Hi @GabiGrin — is #112 still funded for a new contribution, and what complete move/rename behavior remains to be fixed after the existing PRs, including #291–#293? Please clarify moves inside VS Code versus outside the editor, the target Flyde/VS Code versions, and the acceptance cases.
The intended result would be working imports after the agreed moves, with regression tests and the short demo required by your bounty guidelines. Is the listed $15 still the total, in which currency, and do the Algora reward/payment terms still apply? Please confirm payout eligibility, fees and timing. With those details I can assess the full remaining scope before starting.
2022117144 commentedon Oct 22, 2026
/attempt #112
I have implemented a focused fix against the current
source.type=fileflow format: participate in VS Code rename operations, update incoming file references and rebase outgoing references when the parent moves, while preserving YAML comments and unsaved edits. The branch includes 12 path regression tests and four real extension-host rename scenarios (all passing on VS Code 1.87.2). The patch does not claim to handle file moves made outside VS Code or migrate legacy imports.Branch: https://github.com/2022117144/flyde/tree/fix/flow-imports-on-rename
AI-assisted contribution; I will link the PR with validation and a short demo walkthrough.
Fix flydelabs#112: Broken imports after moving files
schwankeith commentedon Oct 25, 2026
/attempt #112
Fix flydelabs#112: Broken imports after moving files
sonofkratos92 commentedon Oct 27, 2026
/attempt #112
Listening to
vscode.workspace.onDidRenameFilesin the VS Code extension to recompute relative file paths for imported code nodes and visual subflows whenever an imported file, directory, or.flydeflow file is moved or renamed.heroking777 commentedon Oct 27, 2026
/attempt #112
lsdkyu commentedon Oct 27, 2026
/claim #112
PR: #300
Fix: adds onDidRenameFiles listener to auto-update .flyde import paths when files are moved.