feat(fast-element): attached behaviors #2784
Merged
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.
Description
This PR refactors the
RefDirective
into a general purposeAttachedBehaviorDirective
which opens up new possibilities for attaching arbitrary custom behavior to any HTML element within a template.Motivation & context
When reflecting on the way that the
ref
binding works, it occurred to me that the base functionality could be parameterized slightly to result in a whole new extensibility point within the templating engine. With that in place,ref
could be built on top of a lower-level API and other "attached behaviors" could also be built rather easily.NOTE: This PR also makes
ref
a standard export of the library.Issue type checklist
Is this a breaking change?
This is technically a breaking change because
RefDirective
no longer exists. However, that was not likely used by anyone directly. It was used internally by theref
function. This function, which is used in most templates, has remained unchanged, in terms of its signature and intended usage.Process & policy checklist