Simone D'Avico

@davezuko I am trying to achieve the same as you suggested, but it somehow breaks routing. This is what I did: - Create a `apphistory.js` module where I create my...

@jenyckee yes, I got it working with the approach described in my previous comment.

@amergin calling `useRouterHistory` to create a custom history as showed above it's really all there is to it. You only have to be careful to create it as a singleton.

@amergin yes, you import `createBrowserHistory` from that path. Then, you create a custom history in a module you create (e.g., `apphistory.js`): ``` javascript const historyConfig = { basename: __BASENAME__ };...

The `onEnter` approach you mention is fine to load data when a route is entered. What do you mean by "the routes are all declared dynamically"? The routes are declared...

> Adding > > ``` > user: ":" > ``` > > for `docker-compose` (or `--user ":"` for `docker`) seems to fix this for me. You can look these up...

Maybe we could look at how others do it to be sure of taking into account every option? As I mentioned in #28, light-server offers a similar feature :)

@zibs Actually, my goal is exactly to have something that resembles more closely the new BiometricPrompt implemented by Android P. Unfortunately, there are a few problems with the new Biometrics...

@pulpfree the client is available in the `context` parameter of the resolver. I am also facing the same use case and wonder if this is the right way to go...

> The ONLY way I can think of handling this, currently, is for all tests to add a `` wrapper. I can probably add this feature, but would need help...