simple_routes 1.0.0-beta.9 
simple_routes: ^1.0.0-beta.9 copied to clipboard
andyhorn.devSimple, declarative route and navigation management for go_router.
Simple Routes #
Simple, declarative route and navigation management for go_router.
Stable release #
We have reached a stable release of Simple Routes with v1.0.0! 🎉
This release includes several breaking changes from the 0.x.x versions.
Please see the Migration Guide for more info.
Features #
Simple Routes is a companion package to GoRouter that provides a simple, type-safe way to define your app's routes and navigate between them.
- Eliminate "magic strings" and the bugs that come with them
- Simplify route definitions and navigation invocation
- Enforce type-safe routing requirements
- Inject and extract path parameters, query parameters, and "extra" route data
Table of Contents #
Getting started #
This package is intended to be used with the GoRouter package.
dependencies:
go_router: ^12.0.0
simple_routes: ^1.0.0-beta.7
Usage #
Route definitions #
Basic (simple) routes
Define your routes as classes that extend the SimpleRoute base class and override the path property with the route's path segment.
class ProfileRoute extends SimpleRoute {
const ProfileRoute();
@override
String get path => 'profile';
}
No need to add the leading slash for a root-level route; if your route is not a child route (more on this below), the leading slash will automatically be added, when necessary.
Route path segments
If your route contains more than one path segment, build your path using the fromSegments method.
class UserProfileRoute extends SimpleRoute {
const UserProfileRoute();
@override
String get path => fromSegments(['user', 'profile']);
}
When in debug mode (or in tests), this method will check for duplicate segments and throw an assertion error if any are found.
Route parameters and DataRoutes
For routes that require parameters, extend DataRoute instead. This will allow you to define a data class that will be used to pass data to your route.
For example, let's create a class that we want passed between routes using GoRouter's "extra" property.
// Some class or object that you want to pass with your route.
class MyExtraData {
const MyExtraData(this.someValue);
final String someValue;
}
Next, we'll need to define our route parameters in an enum.
// Define any route parameters and query parameters as enum values.
// These will be used to match path parameters in the template and
// add query parameters to the URL.
enum RouteParams {
userId,
query,
}
Next, let's define our route data class.
// Define a data class that extends SimpleRouteData
//
// This class should carry any data that your route requires,
// including path parameters, query parameters, and
// "extra" data that you want to pass to your route.
class UserRouteData extends SimpleRouteData {
const UserRouteData({
required this.userId,
required this.extraData,
this.queryValue,
});
// For example, a "user ID" parameter for the path
// e.g. /user/:userId
final String userId;
// Or a query parameter
final String? queryValue;
// Or any other data that you want discretely passed to your route.
final MyExtraData extraData;
// Override the `parameters` property with a map of your
// route's path parameters (identified by the Enum).
@override
Map<Enum, String> get parameters => {
RouteParams.userId: userId,
};
// Override the `query` property with a map of your route's
// query parameters. These will be automatically URL encoded
// and appended to the end of your path.
//
// The query map allows null values, so you don't have to worry
// about whether or not to include a query parameter.
@override
Map<Enum, String?> get query => {
RouteParams.query: queryValue,
};
// Override the `extra` property with any extra data that you
// want passed along with your route.
@override
MyExtraData get extra => extraData;
// Use a factory constructor to simplify extracting data from
// the GoRouterState in a redirect or builder callback.
factory UserRouteData.fromState(GoRouterState state) {
// Use the extension methods to simplify extracting
// data from the GoRouterState.
final userId = state.getParam(RouteParams.userId)!;
final queryValue = state.getQuery(RouteParams.query);
final extraData = state.getExtra<MyExtraData>()!;
return UserRouteData(
userId: userId,
queryValue: queryValue,
extraData: extraData,
);
}
}
Finally, we can define our route, extending the DataRoute class.
// Define the route as a DataRoute, typed for your data class.
class UserRoute extends DataRoute<UserRouteData> {
const UserRoute();
// Define the route path using the appropriate enum value.
// Use the `prefixed` property to automatically prefix the
// enum value name with a colon (e.g. ":userId").
//
// To define a path with multiple segments, use the `fromSegments`
// method to join the segments with a forward-slash.
@override
String get path => fromSegments(['user', RouteParams.userId.prefixed]);
}
Because this route is a "data route," we must provide it with an instance of its route data class when navigating. More on this in the Navigation section.
Please note that the parameters, query, and extra overrides are entirely optional, depending on your use-case.
Child routes #
To define a route that is a child of another route, implement the ChildRoute interface, providing the parent route type and overriding the parent property.
class UserDetailsRoute extends DataRoute<UserRouteData> implements ChildRoute<UserRoute> {
const UserDetailsRoute();
// Define the route path segment. No need to worry about
// leading slashes - they will be added automatically.
@override
String get path => 'details';
// Define the parent route. This will be used to
// construct the full path for this route.
@override
UserRoute get parent => const UserRoute();
}
Note: Routes that are children of a DataRoute must also be a DataRoute themselves, even if they don't require any data. In cases like these, you can re-use the parent's data class and factory constructor.
However, if they require their own data, the data class must provide it and the data necessary for the parent(s).
GoRouter configuration #
Configuring GoRouter is easy. When defining a GoRoute, create an instance of your class and pass the goPath property to the path parameter.
GoRoute(
path: const HomeRoute().goPath,
),
Below is a full example of a GoRouter configuration, including a route protected by a redirect and extracting data from the GoRouterState in a builder callback.
GoRouter(
// Note that the initialLocation should use the "fullPath" property
// to include any parent routes, if applicable.
initialLocation: const HomeRoute().fullPath,
routes: [
GoRoute(
path: const HomeRoute().goPath,
builder: (context, state) => const HomeScreen(),
),
GoRoute(
path: const UserRoute().goPath,
redirect: (context, state) {
// Use the extension methods to validate that any and all
// required values are present.
if (state.getParam(RouteParams.userId) == null) {
// If the data is not present, redirect to another route
// using the `fullPath` method - this is important,
// as the `path` and `goPath` properties only include the
// route's segment(s), but not the full URI.
return const HomeRoute().fullPath();
// Note: If you're redirecting to a data route, the `fullPath`
// method will require an instance of your route data object.
// For example:
// return const UserRoute().fullPath(UserRouteData(...));
//
// See the "DataRoute generation" section below.
}
// If all of the data is present, return null to allow the
// route to be built.
return null;
},
builder: (context, state) {
final routeData = UserRouteData.fromState(state);
return UserScreen(
userId: routeData.userId,
query: routeData.queryValue,
extra: routeData.extraData,
);
},
routes: [
// Define the child route, using the same data class as
// the parent route.
GoRoute(
path: const UserDetailsRoute().goPath,
builder: (context, state) {
final routeData = UserRouteData.fromState(state);
return UserDetailsScreen(
userId: routeData.userId,
);
},
),
],
),
],
);
DataRoute generation
If you need the full path of a DataRoute, such as for generating a link or redirect, you will still use the fullPath method, but it will require an instance of your route's data class.
For example, given the following route:
class MyRoute extends DataRoute<MyRouteData> {
const MyRoute();
@override
String get path => fromSegments(['user', RouteParams.userId.prefixed]);
}
The fullPath method will require an instance of the MyRouteData class.
redirect: (context, state) {
return const MyRoute().fullPath(MyRouteData(userId: '123'));
}
This will return the full, populated path: /user/123.
Navigation #
Once your routes are defined and your router is configured, you can navigate between your routes using the go and push methods.
onPressed: () => const HomeRoute().go(context),
For your routes that require parameters, the go method will enforce that you pass an instance of your data class.
onPressed: () => const UserRoute().go(
context,
data: UserRouteData(
userId: '123',
queryValue: 'some query value',
extraData: MyExtraData('some extra data'),
),
),
Note: The push method signatures are identical to their corresponding SimpleRoute/DataRoute go methods.
Advanced usage #
Route matching #
Current route
The isCurrentRoute method will determine if your app is at a particular route.
For example, given the following routes:
class BaseRoute extends SimpleRoute {
const BaseRoute();
@override
String get path => 'base';
}
class SubRoute extends SimpleRoute implements ChildRoute<BaseRoute> {
const SubRoute();
@override
String get path => 'sub';
@override
BaseRoute get parent => const BaseRoute();
}
and your app is at the location of /base/sub:
// current location: '/base/sub'
if (const SubRoute().isCurrentRoute(context)) {
debugPrint('We are at SubRoute!');
}
Your app will print We are at SubRoute!.
Parent route
Similar to isCurrentRoute, you can use the isParentRoute method to check whether a route is a parent of the current location.
For example, if your app is at the location of /base/sub:
// current location: '/base/sub'
if (const BaseRoute().isParentRoute(context)) {
debugPrint('We are at a child of BaseRoute!');
}
Your app will print We are at a child of BaseRoute!.
Note: this method will return false if the current route is an exact match for the route in question (i.e. isCurrentRoute).
For example, if we are at the /base/sub location and use isParentRoute, it will return false:
// current location: '/base/sub'
if (const SubRoute().isParentRoute(context)) {
debugPrint('We are at a child of SubRoute!');
}
In this case, the print statement will not be executed.
Active route
If you need to determine if a route is active, but not necessarily whether it is the current route or a parent, you can use the isActive method.
This method will check that the route exists in the current location, but does not discern between being an exact match or a parent match.
For example, if your app is at the location of /base/sub:
// current location: '/base/sub'
if (const BaseRoute().isActive(context)) {
debugPrint('BaseRoute is active!');
}
Your app will print BaseRoute is active!.
If your app is at the location of /base:
// current location: '/base'
if (const BaseRoute().isActive(context)) {
debugPrint('BaseRoute is active!');
}
Your app will still print BaseRoute is active!.
Metadata
Publisher
Metadata
Simple, declarative route and navigation management for go_router.
Repository (GitHub)
View/report issues
License
unknown (license)
