riverpod_generator 3.0.0-dev.11

riverpod_generator: ^3.0.0-dev.11 copied to clipboard

• riverpod_annotation upgraded to 3.0.0-dev.3
• riverpod upgraded to 3.0.0-dev.3

• riverpod_annotation upgraded to 3.0.0-dev.2
• riverpod upgraded to 3.0.0-dev.2

• Fix crash when encountering classes with a ProviderBase field.

• riverpod_analyzer_utils upgraded to 1.0.0-dev.0

• Providers can now be generic:

  @riverpod
  List<T> example<T extends num>(ExampleRef<T> ref) {
    return <T>[];
  }
  
  @riverpod
  class ClassExample<T> extends _$ClassExample<T> {
    @override
    List<T> build() => <T>[];
  }
  

  Specifying type parameters works the same as specifying arguments, and make the generated provider a "function":

  ref.watch(example<int>());
  

• Upgraded to use Riverpod 3.0

• Fixed family.overrideWith missing

• riverpod_analyzer_utils upgraded to 0.4.2

• Annotating a provider with @deprecated and a few other annotations also annotate the generated code accordingly (thanks to @SunlightBro)
• provider.argument is now a record of all arguments in a provider.

• riverpod_analyzer_utils upgraded to 0.4.1
• riverpod_annotation upgraded to 2.2.0

• riverpod_analyzer_utils upgraded to 0.4.0

The code generator now supports import aliases, generated types and typedefs as input of providers!.

This comes with a few minor restrictions:

• Breaking: Returning a Typedef or type Future/FutureOr/Stream is no-longer supported:

  typedef Example = Future<int>;
  
  @riverpod
  Example foo(FooRef ref) async => 0;
  

• Breaking: Arguments of the form fn(void myParameter()) are no-longer supported. Instead use fn(void Function() myParameter).

• riverpod_annotation upgraded to 2.3.3
• riverpod upgraded to 2.4.9

• riverpod_annotation upgraded to 2.3.2
• riverpod upgraded to 2.4.8

• Fix crash when encountering classes with a ProviderBase field.

Fix typos and internal changes

• riverpod_analyzer_utils upgraded to 0.4.1

• riverpod_analyzer_utils upgraded to 0.4.1

• riverpod_analyzer_utils upgraded to 0.3.4
• riverpod_annotation upgraded to 2.1.6

• Disable invalid_use_of_visible_for_testing_member in generated files

• riverpod_annotation upgraded to 2.1.4

• The "ref" object now contains the provider parameters too. This enabled provider.overrideWith to use the provider arguments:

  @riverpod
  int example(ExampleRef ref, {int? id}) { /* */ }
  // ...
  exampleProvider.overrideWith(
    (ref) {
      print(ref.id);
    }
  )
  

• Fix all provider.overrideWith causing a cast error if the notifier receives arguments.

• Support both analyzer 5.12.0 and analyzer 6.0.0

Support analyzer 6.0.0

Disable all lints in generated files.

• riverpod_analyzer_utils upgraded to 0.3.1

• Fix an issue where specifying a dependency on a provider declared in a different file could cause a missing import.

• riverpod_annotation upgraded to 2.1.1

• Added support for Raw typedef in the return value of providers. This can be used to disable the conversion of Futures/Streams into AsyncValues

  @riverpod
  Raw<Future<int>> myProvider(...) async => ...;
  ...
  // returns a Future<int> instead of AsyncValue<int>
  Future<int> value = ref.watch(myProvider);
  

• If a provider has an empty list of dependencies, the generated list is now const (thanks to @K9i-0)

• riverpod_annotation upgraded to 2.0.3

• riverpod_analyzer_utils upgraded to 0.2.0
• riverpod_annotation upgraded to 2.0.2

• Fixed InconsistentAnalysisException
• Fixed an Unsupported operation: Unknown type SimpleIdentifierImpl crash

• riverpod_analyzer_utils upgraded to 0.1.3

• riverpod_analyzer_utils upgraded to 0.1.2

• Added support for configuring the name of providers with parameters ("families") (thanks to @K9i-0)

• Deprecate the (new) shorthand syntax for scoping provider using the external keyword. That syntax unfortunately does not work on web and therefore will be removed.

• Add support for returning a Stream inside providers. This is equivalent to creating a StreamProvider using the "old" syntax.
• Bump minimum riverpod_analyzer_utils version
• Fix exception thrown when the analyzed file has some syntax errors.

• It is now possible to specify @Riverpod(dependencies: [...]) to scope providers
• Marked @Riverpod as @sealed

Upgrade Riverpod to latest

• The generated hash function of providers is now correctly private (thanks to @westito)
• Allow customizing the name of the generated providers (thanks to @trejdych)
• Update dependencies.

Upgrade Riverpod to latest

• Upgrade Riverpod and annotation package to latest

• Update dependencies.

• Update dependencies.

• Update a dependency to the latest release.

Fix version conflict with Riverpod

Initial release