Nimblesite / Nimblesite/SharpLsp
Rename: properties and indexers
Open
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# and F# properties and indexers, including get/set usages, interface implementations, overrides, and references.
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
- 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.
Research direction
Start with docs/specs/RENAME-SPEC.md, then read the rename code-element coverage sections in the linked planning documents. Use those requirements to define support for properties and indexers, including declarations, implementations, overrides, and references. Done means the prepareRename and rename acceptance cases pass, including coarse end-to-end 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
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100