fix: Regenerate yaml, carryTrim => trimSource cleanup (#3121)
PR #2995 didn't take into account the data model storage actually does change when you change a variable name. Boxer yaml generation was missed in earlier PR. * chore: Run `generate-yaml.sh` * chore(cpn): carryTrim -> trimSource * fix(build): Boxer missing from `generate-yaml` * dodgy attempt to read old carryTrim * fix: Don't break the byte boundary + reorder * fix(yaml): indentation for attributes that should not be output * chore: Regenerate YAML after rebase --------- Co-authored-by: raphaelcoeffic <raphael.coeffic@frafos.com>
This commit is contained in:
co-authored by
raphaelcoeffic
parent
4e09bd7b8c
commit
46cc979875
@@ -487,8 +487,9 @@ static const struct YamlNode struct_LimitData[] = {
|
||||
static const struct YamlNode struct_ExpoData[] = {
|
||||
YAML_UNSIGNED( "mode", 2 ),
|
||||
YAML_UNSIGNED( "scale", 14 ),
|
||||
YAML_CUSTOM("carryTrim",r_carryTrim,nullptr),
|
||||
YAML_SIGNED( "trimSource", 6 ),
|
||||
YAML_UNSIGNED_CUST( "srcRaw", 10, r_mixSrcRaw, w_mixSrcRaw ),
|
||||
YAML_SIGNED( "carryTrim", 6 ),
|
||||
YAML_UNSIGNED( "chn", 5 ),
|
||||
YAML_SIGNED_CUST( "swtch", 9, r_swtchSrc, w_swtchSrc ),
|
||||
YAML_UNSIGNED_CUST( "flightModes", 9, r_flightModes, w_flightModes ),
|
||||
|
||||
Reference in New Issue
Block a user