It's easy to imagine an app with multiple config files, where each config file can have fields that specify paths relative to the config file's parent directory. How would BYOC handle this?
The meta information is available to the picker, but that's not the right place to be dealing with things that are specific to individual getters.
The cast function is the right place to deal with this, but it doesn't have the info. I could just add a cast_meta function that gets the metadata as a second argument, but I wonder if there's a more elegant way to deal with this. I don't want to end up proliferating a bunch of cast_xxx functions.
It's easy to imagine an app with multiple config files, where each config file can have fields that specify paths relative to the config file's parent directory. How would BYOC handle this?