Replies: 3 comments
|
There is currently no support for such conditional defaults. In this case may I suggest the simplest solution is to set defaults for a release build ( I guess it would be nice if there were a callback or similar which the application could use to return custom defaults. This happens in A more generic solution might be to support pre-processing with some kind of expression parsing or expression substitution such as |
|
Or maybe add a flag/method to determine if an object or store is using defaults... |
|
I'm currently defining those items as ENUM with an UNDEF/TRUE/FALSE choice and, if they're UNDEF, set them upon first access. That works, but having this part of the build system would be nicer. |
Uh oh!
There was an error while loading. Please reload this page.
Is there possibly already a way of having conditional defaults for configdb?
I'm adding a telemetry function to my firmware (I am seeing uncommanded reboots in the field and want to be able to troubleshoot them) and for that, I've added a mttq based telemetry that I want to default to on for debug builds but to off for release builds.
Is that something that could be done in configdb?
my schema snippet looks like this:
All reactions