Mastersam07/kaisel - 5 Help Wanted Issues

Open Issues Need Help

docs: make the chromeBuilder router-resolution rule harder to trip on about 3 hours ago

documentation good first issue pkg:kaisel

Type-safe Flutter routing with no string paths and no codegen. Routes are sealed classes, your nav stack is a typed list, and the compiler makes sure you handle every screen.

Dart

#dart#flutter#navigation#router

chore: alias set() onto KaiselNavigator for symmetry with KaiselRouter about 3 hours ago

enhancement good first issue pkg:kaisel_core

Mastersam07/kaisel

Type-safe Flutter routing with no string paths and no codegen. Routes are sealed classes, your nav stack is a typed list, and the compiler makes sure you handle every screen.

Dart

#dart#flutter#navigation#router

docs: SHELLS.md should note that a route serving as both tab content and a full screen needs two values about 3 hours ago

documentation good first issue pkg:kaisel

Mastersam07/kaisel

Type-safe Flutter routing with no string paths and no codegen. Routes are sealed classes, your nav stack is a typed list, and the compiler makes sure you handle every screen.

Dart

#dart#flutter#navigation#router

docs: cross-link run<T> from the migration guide's callback-carrying route section about 3 hours ago

documentation good first issue pkg:kaisel

Mastersam07/kaisel

Type-safe Flutter routing with no string paths and no codegen. Routes are sealed classes, your nav stack is a typed list, and the compiler makes sure you handle every screen.

Dart

#dart#flutter#navigation#router

docs: note that auto_route inherited path params become explicit fields on the child route about 3 hours ago

documentation good first issue pkg:kaisel

Mastersam07/kaisel

Type-safe Flutter routing with no string paths and no codegen. Routes are sealed classes, your nav stack is a typed list, and the compiler makes sure you handle every screen.

Dart

#dart#flutter#navigation#router