DAGWorks-Inc
@config.custom for clearer/more powerful config parsing
Is your feature request related to a problem? Please describe.
@config gives no insight/structure into what config items are required, as it takes in the whole thing. Its meant to be internal but exposed externally.
Describe the solution you'd like
@config.custom would
take in the same argument as resolver in @resolve
Describe alternatives you've considered Keeping the current one, not supporting custom functions, keeping the current one as a fallback.
Additional context See Peter Robinson's comments here: https://hamilton-opensource.slack.com/archives/C03M33QB4M8/p1682076384844779
Timeboxed this but there's some weirdness about how we enforce the config that made me not want to deal with this yet...