You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we should add a version value to each generated local config, e.g:
#defineLOCAL_CONFIG_VERSION1
the firmware code could then have following definition & check:
#defineMIN_LOCAL_CONFIG_VERSION1
#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.
The text was updated successfully, but these errors were encountered:
we should add a version value to each generated local config, e.g:
the firmware code could then have following definition & check:
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.
The text was updated successfully, but these errors were encountered: