Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Feature]: Non-solution project analysis

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp, fsharp
Domain
backend

Research direction

Start by reading the project-loading entry points that currently require a .sln or .slnx file and trace how project files are discovered. The issue does not name files or tests, so first locate the solution discovery code and existing project-loading tests. Done means a folder containing .csproj or .fsproj files can be opened without a solution file and those projects are available to SharpLsp.

Written by the indexing model from the issue text.

Description

Problem / motivation

I'm a newcomer to sharplsp. This is wonderful

I was trying to start a new project with codium just like other minimalist developers would do: run dotnet new classlib -lang f# -o ./Template -f net10.0 and open it with codium.

I just found sharplsp requires solution file to work properly. If no solution, .csproj/.fsproj file wont be read.

Proposed solution

Sharplsp still works even without .sln or .slnx. Aka, can use .csproj/.fsproj file instead.

Language relevance

Both C# and F#

Alternatives considered

ionide can do this, when you open a folder without sln or slnx, it can search for .fsproj file. Then it displayed all fsproj in solution explorer.

Dominant language
TypeScript
Stars
168
Forks
9
Avg merge
2h 51m
Merged PRs (30d)
59

Getting set up

Open in Codespaces

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

  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.

More from Nimblesite/SharpLsp

All issues in Nimblesite/SharpLsp

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.