Nimblesite / Nimblesite/SharpLsp

Rename: generic type parameters

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

Nobody has claimed this yet.

.NET cluster:rename
Dominant language
TypeScript
Stars
132
Forks
5
Avg merge
6h 24m
Merged PRs (30d)
27

Description

Scope

Implement rename support for C# type and method type parameters plus F# generic type parameters.

Docs:

  • docs/specs/RENAME-SPEC.md
  • docs/plans/CODE-INTELLIGENCE-PLAN.md#rename-code-element-coverage
  • docs/plans/CSDEVKIT-PARITY-PLAN.md#priority-1----critical-parity-weeks-1-6

Acceptance

  • textDocument/prepareRename returns the correct range and placeholder for this code element category.
  • textDocument/rename returns a WorkspaceEdit that updates declarations and all semantic references across real solution files.
  • Coarse e2e coverage proves success and invalid-name rejection for this category.

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 docs/specs/RENAME-SPEC.md, then read the rename coverage sections in docs/plans/CODE-INTELLIGENCE-PLAN.md and docs/plans/CSDEVKIT-PARITY-PLAN.md. Run the existing coarse end-to-end coverage to understand its conventions. Done means prepareRename and rename handle C# type and method parameters plus F# generic parameters, update semantic references across solution files, and cover success and invalid-name rejection.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, fsharp, typescript
Domain
devtools
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.