Selective overrides in form definitions

[snawbel]

I have a large schema and I would like to set some of the type: 'string' to textareas. However, if I use both the '*' and modify a key to be 'textarea' in my form definition that field will be duplicated.

Am I missing something? It would be nice to be able to use defaults for all form fields except the ones explicitly modified in the form definition.

[davidlgj]

Hi @snawbel, no you're not missing anything. Currently there is no straight forward way to do this (you can hack it together using the postProcess function)

This is an often requested feature though so I hope to get time to fix it in the future. The plane would be to add an attribute with an object mapping keys to object definitions and use these as defaults regardless of where they end up in the form.

[Dervisevic]

👍 ;)

[iamjohnlong]

Would there be a need to add another attribute? I would think if you use "*" in the form definition and then if you have a form definition that maps to the original default it would just override it in its proper place.