-
Notifications
You must be signed in to change notification settings - Fork 671
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Selector parameter from React Router #82
Comments
Hi @gerhardsletten, that should work fine. If you can provide a runnable example of this not working I'll take a look. |
It works, but should not the items.filter... be cached? In this application I have this list of items, and when I first enter an item it is runned, I then returned back to the list, but when I reenter the same item (same id) the filter-code is runned again. This is where I thought reselect should cache the returned content.. |
Yes, we meant the same thing, sorry if I wasn't clear. By "it should work" I meant it should cache when the arguments haven't changed. Have you checked this question from the FAQ? I will need to see an example where Reselect is not behaving as you expect if I am going to be able to help further. |
Hi, I try to use create a selector with the param from React Router for a Master > Detail application, but it looks like it recalculate it every I go into the Detail-view. Should not this be cached?
(when I return to the Masterview, the id-param of the router will be undefined, but it should equal when I re-enter the Detail-view (and viewing an item with the same ID)
The text was updated successfully, but these errors were encountered: