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

about the useMemoized API description #391

Closed
gcback opened this issue Oct 30, 2023 · 0 comments
Closed

about the useMemoized API description #391

gcback opened this issue Oct 30, 2023 · 0 comments
Assignees
@rrousselGit
Labels
documentation needs triage

Comments

@gcback
Copy link

gcback commented Oct 30, 2023

about the useMemoized API description

I understood the previous sentence to mean that when the keys change, 'useMemoized' creates a new instance and caches it. However, if this is the intended meaning, it seems more appropriate to call 'valueBuilder' again rather than recalling 'useMemoized'. Could it be a simple typo?

�original description

A subsequent call of useMemoized...
"A subsequent call of useMemoized with different keys will call useMemoized again to create a new instance."
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rrousselGit rrousselGit

Labels
documentation needs triage
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@gcback @rrousselGit