Closed hazmat345 closed 6 years ago
Ah yeah. This makes sense why this would be happening. I'm not sure how exactly I can support a corner case like this. Not going to add this on the backlog for 0.3.0. Let me know if it becomes more important.
That's totally fair. Feel free to close this if it's not easily fixable. Might be worth adding a warning to the docs telling people not to do this :smile:
This is interesting for posterity, but I plan on closing this. I have no immediate plans for a more complicated migration strategy for yapconf. When I do, this issue will be addressed by this migration strategy.
Pretty super corner-case here. Not sure exactly what's going on but hopefully you can make sense of it. It also may not be a yapconf problem.
Previously had spec item
config
that was a string. Awesome.Changed
config
to be a dictionary with some items under it. I want one of those items,file
, to inherit the previous value ofconfig
, so I list 'config' as a previous_name forfile
.This seems to break when trying to migrate old configuration files - I think yapconf thinks (correctly!) that
config
should be a dictionary, but it's not in the old version.I changed the
config
dictionary to beconfiguration
in the new spec and things now seem to work. So this isn't pressing, just a little strange.Here's what I have: