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
Right now, yaml serialization often spits out all values regardless of whether or not they are 'set'. While this is explicit and easy to understand, it makes for lengthy files. Perhaps in some cases it is more appropriate to omit the value unless a non-default is specified?
The text was updated successfully, but these errors were encountered:
This issue was discussed during the ACES config working group meeting today. The group agreed that we would prefer that attribute values that are default should not be serialized to the yaml. The ColorSpace bitdepth and allocationvars being common examples. The interpolation value of FileTransforms being another example.
To give an example, if we were to remove default equality_group, is_data, allocation and allocationvars from the current ACES config, it would remove over 1100 lines from 5000, more than a fifth!!!
As pointed out in the meeting, the equality_group not being specified could lead to a bunch of No-Ops, so we may need to clean up the behavioural differences between, not specifying the option, specifying the option but it being empty and specifying the option as an empty string, etc.
Will need to consider if this may break backwards compatibility in v1 configs, etc.
Right now, yaml serialization often spits out all values regardless of whether or not they are 'set'. While this is explicit and easy to understand, it makes for lengthy files. Perhaps in some cases it is more appropriate to omit the value unless a non-default is specified?
The text was updated successfully, but these errors were encountered: