routex 1.0.10

Identify your logic with URI, apply any number of composable asynchronous handlers using intuitive syntax. Supports route navigation. Vert.x like event handling in Flutter.

1.0.10

• Dependencies update

1.0.9

• Default placeholders update

1.0.8

• Dependencies update

1.0.7

• Dependencies and docs update

1.0.6

• Navigator customization options

RoutexNavigator navigator = RoutexNavigator.newInstance(navigator: CustomNavigator());

class CustomNavigator extends RoutexNavigator {
  
  @override
  Future<T> push<T extends Object>(String path, BuildContext context,
          [Map<String, dynamic> params]) =>
      Navigator.push(
        context,
        _pageRoute(builder: asWidgetBuilder(path, params)),
      );
  
  PageRoute<T> _pageRoute<T>({@required WidgetBuilder builder}) =>
      Platform.isIOS
          ? CupertinoPageRoute(builder: builder)
          : MaterialPageRoute(builder: builder);
  
}

1.0.5

• Route with regex:

router
  .routeWithRegex(r"^\/images\/(?<name>[a-zA-Z0-9]+).(jpg|png|gif|bmp)$")
  .handler((context) => context.response().end(context.getParam("name")));

• Mount sub-router:

//support old CountriesController
  var subRouter = Router.router();
  var countriesController = CountriesController();
  countriesController.bindRouter(subRouter);
  router.mountSubRouter("/v1", subRouter);

1.0.4

Important!

RoutexNavigator behaviour change.

Before this version behaviour was if Flutter framework calls returned WidgetBuilder function n times to redraw screen, handlers will be executed same number of times. This is not case anymore.
New behaviour is to call handlers once per RoutexNavigator methods call, so 1 call to RoutexNavigator (get, push, etc. methods) is 1 call to all handlers, and Flutter can recall provided WidgetBuilder functions n times, but handlers will be executed only once. This can be very important and useful, for example, if we push screen once we know that we create objects only once, so Flutter calls of WidgetBuilder function will not affect our state - objects created in handlers.
Be aware of differences between get and push methods, push is used explicitly with some event, and get is used mainly in widget tree by framework.
With RoutexNavigator.get call inside Widget tree only guarantee for some objects to be only once initialized is initState method inside State<T> class, and for RoutexNavigator.push calls objects created inside handlers will also be initialized only once.

1.0.3

• Description update

1.0.2

• Description update

1.0.1

• First version