Extending child contexts with container element #43
+19
−18
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change addresses #39 by extending the child binding context with a
$parentNode
property. The$parentNode
property refers to the - not virtual - container node, which will become the parent node of each item.General usage recommendation for custom bindings which need to access the parent element can be like this.
This technique could be kind of a default workaround for any binding which control child bindings and have such a complex logic that the child nodes are not attached to the DOM yet at binding time.
As far as
FastForEach
goes, it would have been very difficoult to implement a logic to insert the child nodes first, and then bind them.I'm open to any other idea.