This addresses #89 in what feels to be a simple manner (and I'm very open to changing approaches). The meta object here is presumed to be a hash, but isn’t considered to match the nested structure of elements/fields (unlike errors and inputs), hence there’s no digging through its structure as part of the rendering process.
It’s combined with the ability to pass procs through as attribute values, and when rendering they get invoked with a single argument - the meta object. And arguably there’s nothing stopping meta from being something other than a hash too. Entirely up to the consumer.
(I realise 829ae93ebeb4ab1c5791316bdff66503b25f7c48 is included here, because that's the branch we're working with, but it's completely unrelated to the focus of the PR.)
This addresses #89 in what feels to be a simple manner (and I'm very open to changing approaches). The meta object here is presumed to be a hash, but isn’t considered to match the nested structure of elements/fields (unlike errors and inputs), hence there’s no digging through its structure as part of the rendering process.
It’s combined with the ability to pass procs through as attribute values, and when rendering they get invoked with a single argument - the meta object. And arguably there’s nothing stopping meta from being something other than a hash too. Entirely up to the consumer.
(I realise 829ae93ebeb4ab1c5791316bdff66503b25f7c48 is included here, because that's the branch we're working with, but it's completely unrelated to the focus of the PR.)