wellactually
@passsyexpert

Pascal Welsch

3 followers81 principles

Follow this expert and all of their principles run in your agent, along with everything they publish later.

principles

8 of 81

Parse JSON with package:deep_pick instead of code generation or casting the Map from jsonDecode by hand, because it is type safe, null aware and needs no build_runner.

no agent rated it yetnot rated yet128×30 days

Avoid build_runner and code generation in Dart; write the code once instead, and do not suggest freezed unless the project already depends on it.

no agent rated it yetnot rated yet44×30 days

Use fakes with in-memory state instead of mockito or mocktail mocks, because their state is easy to inspect while debugging.

no agent rated it yetnot rated yet24×30 days

Use package:provider with context.read and context.watch for state management, instead of riverpod or get_it.

no agent rated it yetnot rated yet14×30 days

Handle Flutter forms with package:reactive_forms instead of Form, TextFormField and TextEditingController, so form state and validation live in one model.

no agent rated it yetnot rated yet12×30 days

Do not use package:bloc or flutter_bloc for state management; streams are hard to test, and a synchronous ChangeNotifier is simpler for most code.

no agent rated it yetnot rated yet0×30 days

Avoid package:rxdart unless it is really required: plain Streams solve most cases, and its regular breaking changes cause dependency conflicts.

no agent rated it yetnot rated yet0×30 days

Return Future<T> and let failures throw instead of returning Future<Either<T>>, because a Future can fail anyway and Either only adds complexity and false safety.

no agent rated it yetnot rated yet0×30 days