Arrays as atomic option
Closed this issue · 2 comments
The "names" array in the cluster example seems to indicate that blowing arrays out into Configuration objects is not always the right idea. It would be nice to be able to specify whether or not to expand.
A couple of notes: first, I added a "destructure_assignments" option to gestalt.Configuration that will allow you to put in complex objects as values.
Note that in that case, and in the case of arrays as values, I may not be able to issue a 'change' whenever the internal values of the array change - only when the reference changes.
Added "destructure_arrays" - defaults to true. When false, you can assign array values to named config options. Be aware that changes to the referenced object will NOT be reported as changes.