Nicolas Schlecker

access final enum members as const

1

Enhanced enum constructors are required to be `const`. Therefore all final non getter members are implicitly `const` as well. Additionally the index of an enum value is also pre-determined at...

Configurable toString generation

1

I have a few model classes I generate with freezed that have around 30 fields. Only four or five of those are of any value when I log them somewhere....

Support Value Classes for ids

3

Instead of using the `Id` type directly I would like to create value classes for all ids. These Id ValueClasses might look something like this: ```dart class CustomerId { const...

fix: use nullable return type in *OrNull callbacks

1

Close #741

feat: add common properties with different nullability to base mixin

33

The new field `isCommonWithDifferentNullability` might not be perfect but it was the best way I could come up with to propagate the information.

mapOrNull callback return type is non-null

4

Currently the generated `mapOrNull` / `whenOrNull` callbacks specify a non-null return type. ```dart @optionalTypeArgs TResult? mapOrNull({ TResult Function(A value)? a, TResult Function(B value)? b, }) ``` This forces us to...

[NNBD] Null safety migration

9

Null safety is in beta with flutter core support and it's therefore time to start migrating packages as per the [dart migration guide](https://dart.dev/null-safety/migration-guide).

Support drift sqlite syntax

1

[Drift](https://pub.dev/packages/drift) is a persistence library for Dart bases on SQLite. It has introduced some modifications/extensions to the basic SQLite syntax for better code generation. See [drift_files](https://drift.simonbinder.eu/docs/using-sql/drift_files/). Would it be possible...

We're using a lot of value classes for things like ids. Currently `auto_route` does not allow any non primitive types as path/query parameters. I'd like to propose adding support for...

Proposal to make the value of a FormControl non-null

7

Currently when defining a FormControl we usually give it a Type. This type is then made nullable internally in the FormControl. The problem with this approach is that we might...