External F# projects stay unloaded after selecting a C#-only solution
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 52/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- devtools
Research direction
Start with diagnostic-ownership-e2e.test.ts and trace the first adoption interaction for an external F# project. Then inspect the F# ownership gate that requires IsLoaded and how compiler references become ready for an adopted project. Done means the F# error appears exactly once at its actual location while the C# error remains, without a hover, manual request, or restart.
Written by the indexing model from the issue text.
Description
Selecting a C#-only solution leaves the F# compiler slice legitimately empty. Opening a source from a separate, restored F# project then fails to adopt that project, so real errors remain invisible.
Reproduction against feature source 2a59dd10 in the real Windows VSIX host:
- Select a real C# solution containing a compiler-verified CS0029 in a closed file.
- Open a clean source from an external F# project whose other, unopened source has a compiler-verified FS0001.
- Observe Problems without a hover, manual diagnostic request or window restart.
Expected: the F# error appears exactly once at its actual location, while the C# error remains. Actual: the F# report stays empty.
The new diagnostic-ownership-e2e.test.ts reproduces the failure at the first adoption interaction. The current F# ownership gate requires IsLoaded, which is false for a valid selected solution without F# projects. The first adopted project must activate that empty language slice after its compiler references are ready.
- Dominant language
- TypeScript
- Stars
- 168
- Forks
- 9
- Avg merge
- 2h 51m
- Merged PRs (30d)
- 59
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Nimblesite/SharpLsp
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Nimblesite/SharpLsp#468 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Nimblesite/SharpLsp#461 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Nimblesite/SharpLsp#447 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Nimblesite/SharpLsp#444 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Nimblesite/SharpLsp#442 ·
Maintainers usually reply within 1 day
All issues in Nimblesite/SharpLsp
Similar issues
-
freshness freshness:observed-only
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
thoroc/context-radar#282 ·
-
bug P2 rust
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
area: web
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
gabe-santana/arkdraw#25 ·
-
bug require-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
expressjs/expressjs.com#2549 · 1 reaction ·
Maintainers usually reply within 1 day
-
bug good first issue hacktoberfest
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
codercops/discord-bot#101 · 1 comment ·
Maintainers usually reply within 1 day