StimulusReflex::Element and StimulusReflex Targets #687
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.
Feature
Description
Finishes off the proposed StimulusReflex Element and Stimulusreflex Targets features previously started in #489 and #490.
Adds named
element
(the element which called the reflex) and definabletargets
a little bit like theTargets API
in Stimulus, which can be interacted with in reflexes by applying (chainable)cable_ready
operations which can omit theselector
argument, eg:The above examples are all converted automatically into valid
cable_ready
operations against single or multiple targets (collections of targets with the same name), and broadcast at the end of the reflex.Defining targets and scoping targets
By default a reflex will not send targets data from the client side. Targets can be sent by setting the
data-include-targets
property (any truthy value) or targets can be restricted to elements within the parent controller by settingdata-include-targets="controller"
, eg:Checklist