Skip to content

can we have a stable format for settings.json or at least have a mechanism to make it backword compatible? #1548

@pravi

Description

@pravi

Description of the problem or steps to reproduce

Use micro 2.x and 1.4 interchangeably leads to crash of

Details here https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952111#10

Ideal thing would be to not change the settings.json often or if it has to make it in a way that older versions can ignore things it does not understand. or at the minimum give a better error message if settings.json format is not understood. Having versions for the settings.json format will help to check compatibility easily.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions