I removed the restriction of a maximum distance between parent and child form member template ( was 6, why not 42? :smile: )
See PR below.
I think that , still, there is too much magic in finding the parent template.
What would you think of a PR that does away with the nessesary context template parameter and restricts the set of templates looked at to Views which are child views of Templates registered, but not of unregistered templates
Assume a structure of blaze views is like this
view (== Template.view of a registered form template)
Ok, i'm piling up some PRs. @jonjamz Could you have a brief look into the commits so far, so that i know if i have to recreate a PR with only a subset of my changes.
Hi,
I removed the restriction of a maximum distance between parent and child form member template ( was 6, why not 42? :smile: )
See PR below.
I think that , still, there is too much magic in finding the parent template. What would you think of a PR that does away with the nessesary
context
template parameter and restricts the set of templates looked at to Views which are child views of Templates registered, but not of unregistered templatesAssume a structure of blaze views is like this
== Template.view
of a registered form template)== with
for example)== unregistered Template
, providingcontext
)== child view
)Now i'm proposing would pick the parent context
child view
like thisstandalone==true
then don't go up the treestandalone==true
Templatecontext=
data member, than take that onereactiveForms
instance propertystandalone==true
Template, take thisThe docs would read sth. like this
ReactiveElement
takes it's context from the parentReactiveElement
standalone=true
standalone = "recursive"
[or just anything truish, excepttrue
]Do you want to get a PR for this?