[ceoloide]

Add local file loading functionality to Welcome.tsx for YAML, JSON, ZIP, and EKB files, including footprint extraction and conflict resolution.

This PR introduces a new "From Local File" option, enabling users to upload configuration files directly. For .zip and .ekb archives, it extracts config.yaml and any .js files from a footprints/ directory, naming them based on their relative path. Existing conflict resolution logic is reused for footprints, similar to GitHub-loaded injections.

---

 

---

Note

Adds local file upload (YAML/JSON/ZIP/EKB) with footprint extraction and conflict-aware injection processing, plus tests.

• Welcome UI (src/pages/Welcome.tsx):
  • Add "From Local File" option with hidden file input and handler to load configs (.yaml/.yml/.json/.zip/.ekb).
  • Generalize processFootprints to handle GitHubFootprint[] | LocalFootprint[] and integrate with existing conflict resolution flow.
  • Wire up loading state, error handling, and file input reset.
• Utils (src/utils/localFiles.ts):
  • Implement loadLocalFile to parse config files directly or extract from archives.
  • Extract .js footprints from footprints/ in archives, preserving relative names, return { config, footprints }.
• Tests (src/utils/localFiles.test.ts):
  • Add comprehensive tests for YAML/JSON, ZIP/EKB archives, missing config.yaml, nested footprints, and non-.js filtering.

^{Written by Cursor Bugbot for commit 309aa01. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
_{Learn more about Cursor Agents}

[cursor]

This PR is being reviewed by Cursor Bugbot

Details

You are on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

[cursor]

Bug: Conflict dialog leaves loading state active UI bug

When processFootprints encounters a conflict and shows the conflict dialog, it returns early without calling generateNow(). However, the finally block in handleLocalFile only resets isLoading but not isGenerating. This leaves isGenerating=true while waiting for user input on the conflict dialog, causing the UI to incorrectly display a loading/generating state. The finally block should also call setIsGenerating(false), or there should be a check to reset isGenerating when a conflict dialog appears (similar to how handleConflictCancel resets both states).