Passing routes to components

@spectras wrote:

I was wondering whether someone had a better plan for this problem.

I often find myself buidling components to list some data. For instance, they will look like:
{{article-list articles=section.articles delete=(action "delete")}}

The idea is I have several places that need to list articles, and they can do so neatly, using the dedicated component. So far so good.

Now, this listing often includes some actions and links. For instance, every line could include a view, rename, delete action. Such actions go up flawlessly… until some of them need to trigger routes.

How would I do that? I came up with the following solutions, but none seems very clean:

• Forbid links. If triggering a route is needed, then pass an action from the controller, that will do this.transitionToRoute. Feels clumsy, but this is what I end up doing atm.
• Pass the route name to the component. However, that means the component must be aware it is a route name and not an action.
• I posted https://github.com/emberjs/rfcs/issues/105. I believe this would solve the issue by allowing passing (link-to) closures that would behave as actions.

But maybe there is another, better option?

Posts: 3

Participants: 2

Read full topic