riverpod_generator 3.0.0-dev.18

riverpod_generator: ^3.0.0-dev.18 copied to clipboard

• Handle analyzer 8.0
• Fix invalid generated code when a Notifier uses static const as default value for some of its build parameters.
• Support records with a single value.
• Set the default for provider_name_strip_pattern to Notifier$.

• Fixed a conflict between public and private providers of the same name
• Allow passing persist(key: ...)
• Bump minimum meta version
• Support @Riverpod(name: ...)
• Add provider_name_strip_pattern build option
• Bump minimum meta version
• Support @Riverpod(name: ...)
• Added MutationState.isPending/isIdle/hasError/isSuccess
• fixes various "pause" issues
• Bump minimum meta version
• Added AsyncValue.retrying, to check when a retry is scheduled or pending
• Exposed the default retry implementation (ProviderContainer.defaultRetry)
• Offline's Storage now is base and requires overriding deleteOutOfDate
• Make AsyncValue.copyWithPrevious @internal. This API was not meant to be public.

Reworked Mutations to be independent from code-generation

• riverpod upgraded to 3.0.0-dev.15

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

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

• Breaking Removed support for @riverpod external int fn();.

• Breaking Family arguments are no-longer available on the Ref object. The various override methods now take two parameters:

  @riverpod
  String example(Ref ref, int arg, {required int anotherArg}) {...}
  // ...
  exampleProvider.overrideWith(
    (ref, ({int arg, int anotherArg}) args) {
  
    }
  )
  

• Added support for mutations. See also @mutation for further information.

• Added support for @Riverpod(retry: ...)

• riverpod_analyzer_utils upgraded to 0.5.10

Support latest analyzer

• riverpod_analyzer_utils upgraded to 0.5.8

• riverpod_analyzer_utils upgraded to 0.5.7

• Support analyzer >=6.7.0 <7.0.0 This should make it compatible with Flutter's stable channel.

• Deprecated the generated Ref subclasses. Instead of:

  @riverpod
  Model foo(FooRef ref) => ..
  

  Do:

  @riverpod
  Model foo(Ref ref) => ..
  

• @Riverpod(dependencies: [...]) now respects build.yaml options

• riverpod_analyzer_utils upgraded to 0.5.4

• Correctly set minimum support analyzer version to 6.5.0

• Support analyzer 6.5.0

• Adds provider_name_prefix and provider_family_name_prefix to build.yaml. (thanks to @ValentinVignal)
• Generated providers are now always const.
• Added support for abstract build method on Notifiers:

  @riverpod
  class Example extends _$Example {
    @override
    int build();
  }
  

  This is equivalent to writing:

  @Riverpod(dependencies: [])
  class Example extends _$Example {
    @override
    int build() => throw UnimplementedError();
  }
  

• Added support for documentation and annotations on providers/parameters. Comments on providers and family parameters will be injected in the generated code, for IDE documentation in the relevant places. Annotations will be pasted over, such as to mark parameters as @deprecated everywhere.
• Updated to support latest riverpod_analyzer_utils

• 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_analyzer_utils upgraded to 0.5.1

• Improved error handling if:
  • a Notifier has no default constructor
  • a Notifier has has a default constructor but with required parameters
  • a Notifier is abstract

• 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.

1.0.4 #

• Update dependencies.

• Update a dependency to the latest release.

Fix version conflict with Riverpod

Initial release