From 1c5ea020d621e6de3ac6b3c52550574754461b0a Mon Sep 17 00:00:00 2001 From: Chris Reeves Date: Mon, 30 Jan 2017 12:51:08 -0500 Subject: [PATCH] fix typo in proxy events and add deprecation notice for dynamic names in proxy events fixes ractivejs/ractive#2850 closes ractivejs/ractive#2849 --- docs/0.8/Proxy events.md.hbs | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/0.8/Proxy events.md.hbs b/docs/0.8/Proxy events.md.hbs index a0845aa..6711ed4 100755 --- a/docs/0.8/Proxy events.md.hbs +++ b/docs/0.8/Proxy events.md.hbs @@ -82,13 +82,15 @@ Note: the built-in {{{createLink 'lifecycle events'}}} are **reserved**, which m ## Dynamic proxy event names +__Note:__ This functionality is deprecated and will be removed in 0.9. If you need dynamic event names to fire, you can use a method event calling fire with an expression for the name. If you just need an event to be dynamically subscribed, you can place it in an `\{{#if}}` conditional. + {{{createLink 'Mustaches' 'Mustache references'}}} can be used as proxy event names: ```html ``` -In practive this is of limited value, but a more important side effect is that if no handler is specified (a falsey value) the DOM event is not subscribed and will unsubscribe or resubscribe as the handler value changes. Combined with a conditional section, this allows a proxy event to be conditionally subscribed _at the DOM level_: +In practice this is of limited value, but a more important side effect is that if no handler is specified (a falsey value) the DOM event is not subscribed and will unsubscribe or resubscribe as the handler value changes. Combined with a conditional section, this allows a proxy event to be conditionally subscribed _at the DOM level_: ```html