Moniker schema versioning
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- tooling
Research direction
The issue names no files, tests, or entry points. Start by reviewing the LSIF metadata and Moniker.scheme concepts, along with the related discussion in #10. Done means reaching and documenting a decision on whether schema versions belong in metadata and how mismatches should be detected.
Written by the indexing model from the issue text.
Description
As the languages evolve and/or exporter defects are fixed, we may end up in situations where we want to revise the schema used for monikers. LSIF exporters can trivially achieve that by appending a version number to Moniker.scheme value.
Changing the moniker schema would render old LSIF dumps incompatible (unlinkable) with newer LSIF dumps though.
Should then the moniker schema version be a high level concept that is advertised in LSIF metadata so tools can detect mismatches more effectively?
(Note that #10 discussed similar but actually different question about embedding the source code package version in the moniker.)
- 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 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
mksglu/context-mode#1200 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
jaegertracing/jaeger-ui#4506 ·
-
area:desktop area:ui bug platform:macos
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
anthropics/claude-code#96687 ·
-
good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
AOSSIE-Org/DebateAI#582 · 2 comments ·