[GitHub] brooklyn-server issue #1014: [WIP] Subtype setting config val: use as key’...
Github user ahgittin commented on the issue:
Fixed that last problem in my PR, a few `StructuredConfigKey` methods weren't getting invoked when it was wrapped as a `BCKOverwriting`. See 731b9adfccd3dbc7c7bdacec0f89e85d88cfa22e . The default value doesn't include flag-set values, but we can live with that I think -- broken test added for reminder at 9374ecd20eeebf81567135b3b90a2740ab79f789.
So I think the only outstanding thing is ensuring non-visible ancestor config keys are not even seen as keys when resolving.