Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Moniker schema versioning #46

Open
LukaszMendakiewicz opened this issue Jun 10, 2019 · 2 comments
Open

Moniker schema versioning #46

LukaszMendakiewicz opened this issue Jun 10, 2019 · 2 comments
Labels
feature-request Request for new features or functionality
Milestone

Comments

@LukaszMendakiewicz
Copy link

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.)

@dbaeumer
Copy link
Member

That is an interesting question. Would that version be semantic versioned (e.g. 1.1 still ok with 1.2 ?)

@dbaeumer
Copy link
Member

This is still something we should tackle before 1.0.

@dbaeumer dbaeumer added this to the Next milestone Oct 28, 2020
@dbaeumer dbaeumer added the feature-request Request for new features or functionality label Oct 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Request for new features or functionality
Projects
None yet
Development

No branches or pull requests

2 participants