DEV: Make outletArgs available as regular arguments in PluginOutlet #32742
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.
Historically, plugin outlet arguments had to be accessed like
@outletArgs.foo
in templates, orthis.args.outletArgs.foo
in javascript. Following this commit, outletArgs will be passed to connectors at the top level, so they can be accessed like@foo
in templates orthis.args.foo
in JS.@outletArgs
remains available for compatibility, and there are no plans to remove it.For custom classic component connectors, these new arguments may clash with functions/fields defined on the component class. This rare case will be automatically detected, protected against, and a deprecation will be shown.