Merge pull request #177 from Parrryy/teach-passing-actions

Improve explanation of passing actions (#162)

Author: jayjayjpg

guides/v3.4.0/components/passing-properties-to-a-component.md

@@ -54,6 +54,21 @@ known as being "bound"). That is, if the value of `componentProperty`
 changes in the component, `outerProperty` will be updated to reflect that
 change. The reverse is true as well.
 
+In addition to making properties available, actions can be made available
+to components. This allows data to flow back up to its parent. You pass actions
+like this.
+
+```handlebars {data-filename=app/templates/index.hbs}
+  {{button-with-confirmation
+    text="Click here to unsubscribe."
+    onConfirm=(action "unsubscribe")
+  }}
+```
+
+It is important to note that actions can only be passed from a controller or another
+component. They cannot be passed from a route. See [passing an action to the component](../triggering-changes-with-actions/#toc_passing-the-action-to-the-component)
+for more details on how to pass actions.
+
 ## Positional Params
 
 In addition to passing parameters in by name, you can pass them in by position.

guides/v3.4.0/components/triggering-changes-with-actions.md

@@ -192,7 +192,8 @@ to trigger behavior.
 
 That makes it easy to remember how to add an action to a component. It's
 like passing an attribute, but you use the `action` helper to pass
-a function instead.
+a function instead. Actions can only be passed from a controller or 
+component, they cannot be passed from a route.
 
 Actions in components allow you to decouple an event happening from how it's handled, leading to modular,
 more reusable components.