Investigate of abstract properties need reference links
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- devtools
Research direction
No files, tests, or entry points are named. Start by tracing how reference links are generated for TypeScript properties, then compare abstract properties implemented with getters or setters. Done means deciding and documenting whether those abstract properties should receive reference links, with a focused test if the project identifies an appropriate test location.
Written by the indexing model from the issue text.
Description
In TypeScript abstract properties can be implemented using a getter / setter function hence it would make sense to have a reference link for them since they can be bound polymorphically.
- Dominant language
- TypeScript
- Stars
- 198
- Forks
- 40
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 1
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.
More from microsoft/lsif-node
-
feature-request
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
feature-request
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
InlayHint for LSIF Openfeature-request
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
feature-request
Difficulty 4/5 3-5 days Newbie friendliness 30/100
All issues in microsoft/lsif-node
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
danielmiessler/LifeOS#2218 ·