Feature request — dynamic action types

[amplitude]

Feature request — dynamic action types

[RohovDmytro]

Is this something you've seen other libraries support?

No 😸 But I feel no practical need to look up for redux-form actions.

I feel like a better way to solve this problem is to get the redux log visualizer to support custom (action) => description transforms.

Thanks for idea.

[ryanashcraft]

@rogovdm Haha I feel your pain. But I don't feel good about the idea. Is this something you've seen other libraries support? I feel like a better way to solve this problem is to get the redux log visualizer to support custom (action) => description transforms.

[bravo-kernel]

First of all, awesome library. I'm using it to generate generic requests to various (feathersjs) endpoints and must say that I am mighty impressed 💯 .

Hope you don't mind but... are you folks saying that it is possible to configure the log visualiser so that the various actions become more distinguishable (by e.g. using a description) ? If so, a pointer would be more than appreciated.

If not, would reconsidering be an option? Why I'm asking:

1. I currently don't get how to start a saga for a specific action type (could be my novice level)
2. I think it would improve the visuals a lot. A library that supports prefixing is feathers-redux. In this screenshot it is producing results for the messages service/API endpoint. For the projects service it would become e.g. SERVICES_PROJECTS_FIND_PENDING

I think they have chosen a pretty good default here. Things stay very consistent (and library-recognizable) because the end-user can only pass/set the (optional) service name. I can imagine something similar for redux-query:

@@query/REQUEST_USERS_SUCCESS
@@query/REQUEST_PROJECTS_SUCCESS

[rctbusk]

Hey @bravo-kernel! Sorry for the late response. Let me do some research and think about this more and get back to you!

[bravo-kernel]

No problem, thanks for giving this some thought. No rush either, take your time 👍

[karevn]

@rg4real why don't you just create a catch-all saga and then route redux-query related actions based on their query keys or meta values? You can also dispatch your custom-named actions from there, and IMO it's a much better design due to better separation of concerns.

[rctbusk]

@bravo-kernel, for now, I do not think this is something the team is going to invest in terms of new features are concerned.

To solve your problem, I think @karevn has the right idea.

[bravo-kernel]

@rctbusk no problem at all. I had already implemented a saga based alternative before I asked here, I was just hoping I could on-board this project. Anyway, very nice job on the library and your docs inspired me to start using docusuarus as a bridge; https://docusaurus-powershell.netlify.com/). In short.. keep up the good work and thanks again for reconsidering 💯