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.

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

I want to use RiverPod but the official website is too simple and needs to be improved #3966

Open
laterdayi opened this issue Feb 8, 2025 · 2 comments
Assignees
Labels
documentation Improvements or additions to documentation needs triage

Comments

@laterdayi
Copy link

I want to use RiverPod but the official website is too simple and needs to be improved

For concepts all provider, every page has a reminder that the page content may expire, so I would like to ask where is the latest usage guide and what stateProvder should I use? notifer ?

Using riverpod for the first time, it is not clear from the documentation how to use the latest api, which is the latest official recommended state definition way

Image

@laterdayi laterdayi added documentation Improvements or additions to documentation needs triage labels Feb 8, 2025
@famasf1
Copy link

famasf1 commented Feb 11, 2025

You should rely on the official example and case study to get the information on the latest API and its usage. And on the more safety and future-proof side. Stick to code-generation and focus on learning what are Notifier and AsyncNotifier. As those will cover just about every use case for Riverpod.

I agree that the documentation could use some improvement. But until 3.0 arrived, most of the content there are still applicable to the latest version of Riverpod as far as i'm concern.

@maxfrees
Copy link

3.0 When will it be released ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation needs triage
Projects
None yet
Development

No branches or pull requests

4 participants