Skip to content
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.

Sign up for GitHub

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

Jump to bottom

A big problem with reselect. #1

Open
acrazing opened this issue Nov 20, 2020 · 2 comments
Open

A big problem with reselect. #1

acrazing opened this issue Nov 20, 2020 · 2 comments

Comments

@acrazing
Copy link
Member

What the cache should be?
@acrazing
Copy link
Member Author

  1. If a selector is not marked as cacheable, it well always be recomputed
  2. A cacheable selector should be created by selector(fn, cacheKey, type?)
  3. Cache is in store, rather than in useSelector
  4. the last result is always cached of a cacheable selector, with useSelector, every call of select should be called with select(current, previous) to drop the outdated caches.

@acrazing
Copy link
Member Author

acrazing commented Nov 25, 2020 •
edited
Loading

Think about the box:

How to work with mutable map?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@acrazing