Home/ Questions/Q 8785445
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-13T21:21:46+00:00

Today I have come to a shocking discovery: actions referenced on a view are

  • 0

Today I have come to a shocking discovery: actions referenced on a view are handled by their route, not by the view which referenced it. Ex:

<a href="#" {{action edit}}>Edit this</a>

The edit action must be defined in the Route, not in the View. When I was not using a Router before the View was the one responsible for handling such events and I was really happy about it.

Can anyone please:

  1. explain to me why the Route must handle the event, and what are the benefits of this
  2. tell me how can I give control back to the View in matters of handling such actions/events?
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Set the target as view

    <a href="#" {{action edit target="view"}}>Edit this</a>

    If your action is in controller then use

    <a href="#" {{action edit}}>Edit this</a>

    Default target refers to the view’s controller

    I’d suggest you to go through this Reference: Ember Action Helper

    I’d like to mention some key points as per the above reference

  2. In a typical Ember.Router-backed Application where views are managed through use of the {{outlet}} helper, actions will be forwarded to the current controller.
  3. If the action is not defined in the controller, then the current route is targeted.
  • 0