Why @riverpod class NotifierProvider generates to provider #4644
Unanswered
chris-prenissl
asked this question in
Q&A
Replies: 1 comment
-
|
This is one of the 3.0 changes. By default, trailing There's a new configuration in the |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello and thank you for working on riverpod.
Lately we transitioned from riverpod 2.6 to 3.0.3 and after running the build runner
our classes like the following
After
@riverpod
class ExampleNotifierProvider extends _$ExampleNotifierProvider {
@OverRide
String build() {
return 'foo';
}
}
was translated to
exampleProvider
before in 2.6 it was translated to
exampleNotifierProvider
so we have a lot of issues in the project now^^
Is this intended?
Can I influence the naming?
Thank you for responding:)
Beta Was this translation helpful? Give feedback.
All reactions