To support better URL/Deep linking support I'm going to add navigator 2.0 support to dart board

acceptance: In an app with routes "store", "category" and "item=[value]" /store/category=food/item=123

Should resolve 3 Pages and be able to work up the route

1.Routes with data (EqualityNamedRoute) 2. BREAKING! Drop prefix "/" from the route names across sample 3. MaterialApp.router (routerDelegate + routerInformationParser) 4. DartBoardPage class to handle navigator 2.0 routing 5. Example loads a deep route and navigates back correctly 6 . Ability to use your own routerDelegate + routerInformation Parser (personalized state)

• Integration into Example
• Standalone routing example (port of books)

Tracking this in git so I can document status since it's a big upgrade.

The way the code works now is really great the large projects but it’s missing the modern router features.

https://github.com/tomgilder/routemaster Has been and continues to prove valuable . Wen and native Orks Uses the standard context Deep links, share, notifications just works . Relies on unilinks

There are many other navigator 2.0 routers out there also but I liked routemaater because it’s a nice balance between taking over but giving you room to move

The imperative route builder i think fits the needs of dart board also but let you decide

Steps:

1. Launch Playground
2. Change Theme (toolbar should change primary)
3. Enable/Disable "Snow Overlay"
4. Change Theme

Observe, Theme only changes outside the template.

E.g. Missing Dependency

(try to use locator without it added to the feature that uses it).

Give a better error message.

E.g.

FeatureXYZ can not be found, have you correctly registered it in your runner or feature?

Only core is covered 100%, a lot of other modules have stub'd tests.

Acceptance:

• Any PR with an increase to coverage.
• Improvements to the repo (e.g. proper link's and badges in docs)

There is codecov.io enabled to track coverage number's, they can be seen when opening a PR and can aid in writing test coverage.

in DartBoardFeature there is an "enabled" flag, that allows a feature to turn off. E.g. Firebase only works across Android/iOS/MacOS/Web. So I wouldn't want to enable the feature on unsupported platforms.

Currently the solution would be to set "enabled" to a platform check like

  @override
  bool get enabled => kIsWeb || Platform.isAndroid || Platform.isIOS;

You can also disable features manually by calling setFeatureImplementation(featureName, null)

As a framework user, I'd like for a disabled feature to automatically propagate across the feature tree.

E.g. at Feature Linking, prune the tree of implicitly disabled features, whether that be a feature that is explicitly disabled (e.g. with setFeatureImplementation to null, or it's implicitly disabled because of a call to enabled.

Acceptance:

• Be able to disable a high level feature (e.g. redux), observe dependent features being removed (e.g. Minesweeper).
• Be able to disable features via enabled check, e.g. platform check. And propagate that to dependent features. E.g. FirebaseAuth, FirebaseDatabase should disable on Windows/Linux, and features that use them shouldn't be presented (e.g. Chat).