feat(ide): add fbuild ide MVP on stock Zed (#1076 Phase 1) - #1198
Conversation
- `fbuild ide [dir] [-e env] [--no-launch]`: resolves the environment (explicit > persisted .fbuild/ide_state.json > default), installs declared deps via the daemon, refreshes compile_commands.json, emits .clangd + .zed/settings.json via the Phase 0 core, generates .zed/tasks.json (merge-don't-clobber: only "fbuild: "-prefixed task labels are owned; user tasks preserved), and launches Zed (PATH + known install dirs; friendly install guidance when absent, configs still generated). - `fbuild ide select`: interactive environment picker (stderr/stdin, -e bypass), persists the choice and regenerates configs. - daemon_client: new install_deps POST helper + InstallDepsRequest. Part of #1076 (Phase 1). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 38 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (9)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Phase 1 of the corrected #1076 plan: the
fbuild ideMVP on stock Zed, built on the Phase 0 foundations (#1197).What changed
fbuild ide [project_dir] [-e <env>] [--no-launch]— startup lifecycle per the issue: parseplatformio.iniand resolve the environment (explicit-e> persisted.fbuild/ide_state.json> default env), install declared deps through the daemon (POST /api/install-deps, newDaemonClient::install_depshelper), refreshcompile_commands.json(ensure_compile_db(refresh=true)), emit.clangd+.zed/settings.jsonvia the Phase 0 editor-neutral core, generate.zed/tasks.json, launch Zed."fbuild: "— Build, Build (clean), Deploy, Deploy + Monitor, Monitor, Reset, Select environment (runsfbuild ide select). User-authored tasks are preserved; regeneration is idempotent.fbuild ide select— numbered interactive environment picker (stderr prompt/stdin read, same pattern asfbuild sync;-ebypasses for non-interactive use), validates againstplatformio.ini, persists the choice, regenerates DB + configs.Commands::Idewith a nestedIdeAction::Selectclap subcommand;fbuild <dir> idearg-rewrite supported viaKNOWN_SUBCOMMANDS.Validation (local)
soldr cargo test -p fbuild-cli→ 225 passed (18 new module tests + 6 clap-shape tests)soldr cargo clippy --workspace --all-targets -- -D warnings→ exit 0;fmtcleanbash testbefore mergePart of #1076 (Phase 1). Phases 2–4 (daemon-served web panels, probe-rs DAP debug config, native-UI decision) remain on the meta.
🤖 Generated with Claude Code