ember-inspector
ember-inspector copied to clipboard
feature suggestion: detect actions and what module they come from
It would be really helpful if among everything else ember inspector could detect the active actions and their origins.
I love your work btw :)
Thanks :) So you're suggesting a new "Actions" tab that contains a list of actions + controller/route name ?
Yes that would be awesome. Whatever actions are currently active in the route you're in, and their origins.
Yes, this feature would be great! I'm using a plugin as documented but it's not working. I can see the ember actions are bound to the element, data-ember-action="1689", but I can't dig into it any deeper without the suggested tab in the Ember inspector.
Logging actions as they happen (where they were triggered and where they were handled) would definitely be neat.
:+1: for this
I'm interested in working on this. I'd also want it to work out-of-the-box (or maybe v2) with ember-concurrency tasks
I had in mind something like the Redux dev tools which has a history of all actions that go through the reducers
@jasonworden we would definitely love to help you bring your visions to life 😄
I'm doing some issue gardening 🌱🌿 🌷 and came upon this issue. Since it's quite old I just wanted to ask if this is still relevant? If it isn't, maybe we can close this issue?
Actions are being replaced with vanilla functions, so this may not be relevant anymore?
By closing some old issues we reduce the list of open issues to a more manageable set.
@sandstrom I think it's still relevant, but we need someone to want to take it on and work on it.
@rwwagner90 How about adding the 'Discussions' tab and move stuff like that there?
Realistically, many things that are suggested will never be added/built, and having a bunch of open issues makes it less obvious what the "real" issues are.
There is a handy button that can one-click move issues into discussions. One can also up-vote various posts there, to see e.g. interest for various ideas.
Bringing the number of open issues down to a more manageable set of reproducible bugs or other highly relevant stuff makes it easier to focus + get an overview of outstanding issues.
I no longer plan on taking this one up, but looking forward to it making its way into the tool someday!