Nimblesite / Nimblesite/SharpLsp
Rename: F# record fields
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 F# record fields across declarations, construction expressions, copy/update expressions, patterns, and field access sites.
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
Read docs/specs/RENAME-SPEC.md and the linked rename coverage sections in docs/plans/CODE-INTELLIGENCE-PLAN.md and docs/plans/CSDEVKIT-PARITY-PLAN.md. Trace the existing rename and prepareRename entry points, then run the coarse end-to-end coverage. Done means declarations and semantic references across real solution files are updated, with correct ranges, placeholders, and invalid-name rejection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fsharp, typescript
- Domain
- devtools, testing-qa, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100