Repository navigation
Broken imports after moving files #112
Description
Activity
/bounty 15
💎 $15 bounty • Flyde
Steps to solve:
- Start working: Comment
/attempt #112with your implementation plan - Submit work: Create a pull request including
/claim #112in the PR body to claim the bounty - Receive payment: 100% of the bounty is received 2-5 days post-reward. Make sure you are eligible for payouts
❗ Important guidelines:
- To claim a bounty, you need to provide a short demo video of your changes in your pull request
- If anything is unclear, ask for clarification before starting as this will help avoid potential rework
- Low quality AI PRs will not receive review and will be closed
- Do not ask to be assigned unless you've contributed before
Thank you for contributing to flydelabs/flyde!
Attempt Started (UTC) Solution Actions 🟢 @sparkybug Apr 02, 2025, 12:28:08 PM WIP 🟢 @Mira-Mjodheim May 06, 2026, 12:18:06 PM WIP 🟢 @maoshuorz Mar 07, 2026, 03:58:25 AM #256 Reward 🟢 @nexiumbiz-debug May 09, 2026, 01:13:10 AM #260 Reward 🟢 @prashanthnimmagadda May 10, 2026, 10:17:01 PM #261 Reward 🟢 @b0r1v0j3 May 11, 2026, 02:59:14 PM #262 Reward 🟢 @dipespandey May 12, 2026, 09:13:59 PM WIP 🟢 @ldthang0612 May 13, 2026, 05:42:20 AM #263 Reward 🟢 @Gimyoonsoo May 14, 2026, 10:13:57 PM #264 Reward 🟢 @mdp28 May 15, 2026, 06:18:39 AM #265 Reward 🟢 @dukunline-cyber May 17, 2026, 11:57:22 PM #266 Reward 🟢 @nam157 May 19, 2026, 10:21:23 AM #267 Reward 🟢 @ajjucoder May 20, 2026, 03:40:22 AM #268 Reward 🟢 @SeanCordovaGit May 21, 2026, 05:38:57 AM #270 Reward 🟢 @Catnap7 May 22, 2026, 03:20:10 AM #271 Reward - Start working: Comment
/attempt #112
Algora profile Completed bounties Tech Active attempts Options @sparkybug 2 bounties from 1 project Blade, PHP,
JavaScriptCancel attempt @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.
I can take bounty #112. I will share a scoped implementation plan and first PR shortly.
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.
No maintainer response yet on #112, I will switch to another open bounty for now and can resume this issue anytime when feedback arrives.
- added a commit that references this issue
on Mar 7, 2026 /attempt #112
Plan:
- Perform deep trace of the reported issue in the local environment.
- Identify the root cause in the core logic.
- Implement a robust fix with regression tests.
/attempt #112
Plan:
- Reproduce the broken-import case by creating/importing a flow, then moving the imported file to another folder.
- Trace how Flyde stores import references and how the extension resolves them after a file move.
- Patch import resolution/update logic so moved files keep working, with a focused regression test around relative paths.
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.
Submitted PR: #261
/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.
/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.
19 remaining items
/attempt #112
I have prepared a fix using VS Code’s onWillRenameFiles event to update file references through a WorkspaceEdit. It handles dependency moves, importing-flow moves, folder renames, and nested inline flows. Nine focused regression tests cover path handling, including simultaneous moves.
The implementation, tests, and build are ready; I will submit the PR with a short presentation of the actual before/after extension-host test results and the reproducible verification harness. Prepared and tested with OpenAI Codex assistance.
AI-assisted scope audit before attempting #112: I inspected the issue, contribution rules, and the actual diffs/discussion for #256, #259-#271, and #273-#276. I also fetched and tested the strongest current candidates. PR #275 already appears to cover producer, consumer, file/folder, batch, inline-node, dirty-buffer, and package/custom cases, with claimed VS Code host/demo evidence, so I do not want to add another duplicate
/attempt.One reproducibility note: on macOS, #276 compiles and its 11 focused tests pass, but its submitted real extension-host suite finishes with 24 passing / 1 failing. The rename integration test registers a handler while the development extension has already registered the same handler, producing overlapping WorkspaceEdit ranges; this is a test/validation issue, not evidence of a separate product requirement.
Could a maintainer confirm whether #112 requires any behavior not already represented by #275/#276 (for example, recovery after moves made outside VS Code rather than VS Code-originated rename events), and whether the advertised Algora bounty is still funded and claimable? I am not requesting assignment, claiming the bounty, or asserting payout eligibility. If there is no additional intended scope, I will leave this to the existing contributors rather than submit another implementation.
/attempt #112
I am working on a focused VS Code rename handler that updates local file references when a referenced node or its parent folder moves. It will also rebase relative references when the importing flow moves. I plan to use a WorkspaceEdit from the rename event so unsaved editor buffers and undo stay under VS Code's control, preserve YAML formatting, and cover file/folder moves plus nested inline nodes with regression tests.
This is an AI-assisted contribution (Codex) on behalf of the account owner. I will include verification evidence and the requested demonstration with the submission.
Hi — is the advertised $15 bounty for imports breaking after a file move still available to a new contributor? I see existing attempts and want to avoid duplicating them. A submission would use AI-assisted development and include a regression test and demo video. Could you confirm current eligibility, reward availability and whether a completed fix can be reviewed within 48 hours? If this issue is already covered, no action needed.
/attempt #112
Plan: add a rename/move watcher in the VS Code extension that rewrites relative file import paths in .flyde flows (both the moved import target and a moved flow's own imports), using a YAML document transform plus regression tests.
/attempt #112
Plan:
- Reproduce the broken import after moving an imported flow/file between folders.
- Trace how Flyde resolves and persists import paths, then update path resolution so moved files keep valid references.
- Add regression coverage for the move scenario and verify existing import behavior remains intact.
- Submit the required demo evidence with the PR.
/attempt #112
/attempt #112
Plan: reproduce broken relative imports after moving a
.flydeflow between folders in the VS Code extension; implement/adjust rename path rewriting for imported flows and dependent imports; add a focused regression test; open a minimal PR./claim #112
Submitted PR: #282
VS Code
onWillRenameFileshandler rewrites localsource: fileimports (and deprecated top-level import keys) when.flydefiles/folders move, including when the importing flow itself moves. Unit coverage for both directions, folder moves, inline nodes, and batch renames.Hi maintainers — I reviewed issue #112 and the existing file-rename implementation in PR #282. Before starting overlapping work, could you confirm whether the advertised $15 bounty is still available and identify any specific acceptance criterion not covered by the existing PRs? I would only proceed with a distinct, agreed scope and include regression tests plus the required demo. Any contribution from this account would be AI-assisted. This is a scope/funding clarification, not an attempt or bounty claim.
Hi! I've successfully reproduced this issue locally on Windows and reviewed PR #275.
I noticed that a fix has already been submitted. Is there any remaining work, additional testing, or an alternative approach that would be helpful?
I'd be happy to contribute. Thanks!
/attempt #112
Working on a dual-path fix for broken file imports after moves:
- VS Code
onWillRenameFiles+ scalar-only YAML rewrite in@flyde/loader(Explorer renames) - Loader basename-search recovery when the stored path is already stale (external/fs moves)
Focused hermetic tests included. PR incoming.
- VS Code
/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).
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