Hooks?

[naholyr]

Do you plan including hooks "a la react-router" or in some other form?

[tj]

No plan currently, haven't used them myself

[naholyr]

Open to a PR implementing something like this?

• Adds onEnter(nextLocation) and onLeave() attributes
  • onChange(…) could come later but I'd rather start smallish
• Functions can be synchronous or asynchronous (promise)
• Hooks delay rendering

[tj]

Possibly, I haven't found any cases where you'd really need it what are you using them for? Maybe I'm doing something weird haha

[naholyr]

There are two main use cases:

• Checking credentials (you will then not call the callback or not return a promise, or a rejected one, and handle redirection in hook)
• Fetching data (in replacement of component lifecycle method)

[slightlytyler]

@tj where are you handling authentication for a route then? component life cycles?

[tj]

ahh yep I've been just using lifecycle methods for both in little wrapper components like component={authenticated(Dashboard)}. Hooks sound fine but seems easy enough to leave them out as well. I'm mostly 👍 I think since it lets you go more stateless.

I'd also consider just doing something like:

<Authenticated no={this.redirect} yes={this.render} />

in the container(s)

[jarrydfillmore]

+1!

[tj]

kinda like delegating this, closing for now