microsoft / microsoft/lsif-node
Edge from document to packageInformation
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 198
- Forks
- 40
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 1
Description
I want to split documents based on packages, and I think it is only possible via looking indirectly through one of exports, and if a document doesn't have exports we can't find its package. So an edge between document and packageInformation can be helpful.
By the way, packageInformation edge is a good candidate for N to 1 edges (outVs)?
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 by reviewing how document, export, and packageInformation edges are currently represented in the LSIF format and implementation. Define the direct document-to-packageInformation relationship, including whether it is an N-to-1 edge, and verify that documents without exports can still resolve their package.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100