Skip to content

Moniker schema versioning #46

@LukaszMendakiewicz

Description

@LukaszMendakiewicz

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    feature-requestRequest for new features or functionality

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions