It doesn't seem that we're able to get our custom factory to be used to render the input for the child. Nested templates work well of course, but when inside a custom template and rendering a child input for which you want to use a factory instead, locals.inputs[blah] doesn't seem to connect us to our specified custom factory for that input.
So far, we see the only viable options to make this work as being:
a) not using a custom template in the wrapping component (not an option)
b) directly including the component in the custom template and using some other hook for the data binding, a la...
Are we missing something? Is our use case supported or is this not currently possible? If not, is this by design and is there any other workaround you would suggest?
In the end, this turned out to actually be due to a simple (silly) user error. Things do in fact work the way we'd originally hoped. Closing this puppy. Thanks! :)
Hey there. Fascinated with the tcomb* libs. Really appreciate the work you're doing. :smiley: :+1:
Our Situation
Let's say our data model looks something like this...
...and we want to render the form with a custom template which might look like this...
...so far so good. Now, let's say we want to render our child input using not a custom template, but a custom factory:
So our form options might then look something like this...
The Problem
It doesn't seem that we're able to get our custom factory to be used to render the input for the child. Nested templates work well of course, but when inside a custom template and rendering a child input for which you want to use a factory instead,
locals.inputs[blah]
doesn't seem to connect us to our specified custom factory for that input.So far, we see the only viable options to make this work as being:
Are we missing something? Is our use case supported or is this not currently possible? If not, is this by design and is there any other workaround you would suggest?
Thank you!