Pavel Jbanov

It looks like the current implementation of the anchor click interceptor does not support nested elements inside the `a` tag. A couple of workaround options: 1. Use CSS `background` instead...

Are you using route or route_hierarchical package? This was fixed in route_hierarchical.

Are you using route or route_hierarchical?

Currently, in hierarchical branch, query parameters are namespaced -- they must be prefixed with the route name. For example. for URL: `/foo/bar?bar.baz=1234` ``` dart router.root ..addRoute(name: 'foo', path: '/foo', mount:...

You need to return the future from the test. ``` dart test('should do stuff', () { Future foo = doFoo(); return foo.then((value) { expect(value, isCorrect); }) }) ```

There are a couple of use-cases here: 1. shooting yourself in the foot -- probably the one @mhevery is talking about 2. binding overridability controls While I agree with the...

What's the use case?

Use annotations for this. ``` bind(Logger, toImplementation: DbLogger, withAnnonation: const UseDb()); bind(Logger, toImplementation: ConsoleLogger, withAnnonation: const UseConsole()); class MyService { MyService(@UseDb() Logger logger) { ... } } or var loggerType...

@jonaskello A couple of points: - annotations are not DI specific concerns, they are your application specific metadata which you can use to also configure/interact with DI. - annotations (as...

Upstream Dart issue: https://code.google.com/p/dart/issues/detail?id=18675