Ahmed Elsayed

Oh, it's there on dev. Great! I've never needed to use `.value` tbh. To summarize, we might introduce this in the future: - T? `value` → Returns the current value...

@simolus3 I've set `row_class_constructor_all_required` to true but I still have the null properties not required at the generated typedef `XTableCreateCompanionBuilder`. Is there a way to make them required?

The option to make companion properties as required (for inserting) is necessary when using custom dataclass to spot places where I need to decide what to do with the new...

> Currently you can do: > > ```dart > final sub = ref.listen(provider.notifier, (_) {}); > sub.read().someMethod(); > > try { > await Navigator.push(); > } finally { > sub.close();...

Maybe for `.go` we can just do: ```dart try { SomeRoute().go(context); await Future.delayed(someDuration); } finally { sub.close(); } ``` Until [#108764](https://github.com/flutter/flutter/issues/108764) is resolved

> Consider changing the implementation to pass the init parameter(s) in the route and initializing the edit provider in the target page. Initializing the edit provider before navigating is effectively...

Can anyone provide a sample that reproduces this issue?

This issue is because of `toString()` acts differently on debug/release modes. Might be related to https://github.com/flutter/flutter/issues/148983 or wherever `toString` is used from. The unexpected behavior of `child.toString()` on debug/release modes...

This issue is related to `equatable` The `stringify` value defaults to true in debug mode and false in release mode. You can fix it by overriding the global [stringify] setting:...

Furthermore, you might want to rely on `props` for a better search experience: ```dart return item.props.any( (prop) => prop.toString().toLowerCase().contains(searchValue.toLowerCase()), ); ```