The current bundlechanges library handles this by having the default as zero, as you don't specifically have units of subordinates.
We would have to change the bundlechanges library so it also knew whether the charms were subordinates or not in order to correctly handle the missing case.
This involves both callsites getting access to the charms metadata.
A key problem here is subordinates.
The current bundlechanges library handles this by having the default as zero, as you don't specifically have units of subordinates.
We would have to change the bundlechanges library so it also knew whether the charms were subordinates or not in order to correctly handle the missing case.
This involves both callsites getting access to the charms metadata.