Skip to content

Introduce configuration versioning #203

@andre-stefanov

Description

@andre-stefanov

we should add a version value to each generated local config, e.g:

#define LOCAL_CONFIG_VERSION 1

the firmware code could then have following definition & check:

#define MIN_LOCAL_CONFIG_VERSION 1
#if MIN_LOCAL_CONFIG_VERSION > LOCAL_CONFIG_VERSION
  #error You have to update your local config to be able to use this version of firmware
#endif

This would allow us making changes to the config api (e.g. renaming or restructuring the config definitions) which would not lead to compile errors otherwise.
The user would also have an easier to understand error message instead of some generic "XYZ not defined"
If we introduce some breaking changes, we simply bump the min required config version in the firmware ... then adapt the config server and bump the version there as well.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions