TheAngryByrd / TheAngryByrd/MrBuild

Prove bidirectional cross-language source navigation

Open
#16 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

ready-for-agent
Dominant language
F#
Stars
1
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Parent

#10 — Add cross-platform VS Code editor adapter for MrBuild LSP proof

What to build

Use the shared mixed-language fixture to prove source definition navigation in both directions through the public LSP: F# to C# and C# to F#. The editor must land on source files in the selected project graph.

Acceptance criteria

  • Navigating from the selected F# reference lands on the corresponding C# source declaration.
  • Navigating from the selected C# reference lands on the corresponding F# source declaration.
  • The proof exercises the real cross-language symbol routing through the Coordinator.
  • Results resolve to selected-project source rather than metadata-only fallback.
  • The acceptance test reports a clear failure when either language worker or cross-language artifact is unavailable.

Blocked by

  • #14 — Prove editor diagnostics and hover

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the shared mixed-language fixture and the public LSP entry point, then trace cross-language symbol routing through the Coordinator and selected project graph. Add or extend the acceptance test so F# to C# and C# to F# navigation reaches source declarations and reports a clear failure when a worker or cross-language artifact is unavailable.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, fsharp, vscode
Domain
developer-experience, testing
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.