feat: keepAliveRiverpod shorthand #3277
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using Riverpod for state management in Flutter, it is essential to ensure that your code is efficient and easy to read. One way to improve the readability and brevity of your code is to use a shorthand annotation,
@keepAliveRiverpod
, instead of@Riverpod(keepAlive: true)
.The
@keepAliveRiverpod
annotation is a concise way to indicate that a provider should remain active even when not being listened to. It is a simple and clear declaration that is easy to understand and write:Using
@keepAliveRiverpod
makes the intention of your code immediately clear to anyone who is reading it. It is more intuitive than the@Riverpod
parameter and can be easily identified. So, by using@keepAliveRiverpod
, you can improve the readability and brevity of your code.