Vision/Roadmap

[mjackson]

We need to be more effective at communicating our vision for the router. Hopefully we can do this constructively out in the open and get everyone's feedback. Also, I hope this document gives some guidance to people who've asked how they can help.

For now, here's a list of stuff that needs to happen, in no particular order:

• Support trailing slashes. This was originally merged in Support trailing slashes, not extraneous ones #3158, reverted by @timdorr in Revert "Support trailing slashes, not extraneous ones" #3280 (not sure why) and merged again in Support trailing slashes, not extraneous ones #3285. Needs a release.
• Simplify <Link> active semantics (depends on Support trailing slashes, not extraneous ones #3158, see Simplify <Link> active semantics #3231 for discussion)
• Remove nested absolute paths (see Remove support for nested absolute routes #3172 for discussion, [DO NOT MERGE] Deprecate routes with nested absolute paths #3246 for PR). Per @taion's docs in Update decoupling UI from URL pattern #3178, this isn't actually a feature we need.
• Scroll position management. See taion/scroll-behavior for a history enhancer approach. However, I agree with @taion when he says that it's something that needs to be integrated into the router core. I also agree with @ryanflorence when he says that it's very difficult to generalize scroll management, which is why we removed it in 1.0.

As the discussion progresses, I'd like to expand this list, identify changes that we can make together and them into changesets with a release type (e.g. patch, minor, or major) so we can minimize upgrade pain.

Please keep comments short and to the point. Off-topic and excessively lengthy comments will be moderated.

[timdorr]

Re: #3280, that was because of issues like #3279. #3285 has an additional fix for that case.

[taion]

#3158 isn't supporting trailing slashes, it's dropping support for extra slashes. On 2.1.1, /foo/bar matches /foo////////bar//////. Among other problems, paths don't even have a "nearly canonical" form net of the trailing slash.

[taion]

• Support trailing slashes, not extraneous ones #3158 was reverted because it caused a regression when using a basename – useBasename strips the leading slash from location.pathname when the basename has a trailing slash. That's why @timdorr cherry-picked Fix unintentional regressions from removing extraneous slash support taion/rrtr#8, which also adds a test case.
• The change to <Link> would be breaking, and probably needs to come after removing support for nested routes with absolute paths. It's the correct resolution to isActive does not work for optional params #3277, IMO.
• Regex stuff aside, being able to fail to match a route in-place because of "data not found" is IMO a requirement. I think Added condition property to do extra tests on route params, etc. #3098 has a nice API, but again it's blocked on actually fixing Remove support for nested absolute routes #3172 (not just the deprecation warning), so probably needs a major release. Something like https://gist.github.com/ryanflorence/a311ca980c0d8a5d33eab50f29621f12 is extremely unsatisfying.

[timdorr]

For the conditional stuff, what if the onEnter/onChange hooks had a 4th arg that was an error callback?

[taion]

You can already call back with an error. The problem is that those errors can't be caught in a semantic way. Also, raising an error is not as rich as just falling through in routing. I really do think the API in #3098 is quite nice; it does exactly what's needed here.

[timdorr]

I like that one too. Just brainstorming some other options in case there is something more palatable to those that don't like the extra prop.

[taion]

I updated the OP to a checklist, and checked off the two things that we already resolved.

[timdorr]

I'd like to merge @ryanflorence's applyMiddleware into core. No reason not to have it.

[ryanflorence]

I'm making a tweak that @taion and I talked about last night before I make a pull request, it further simplifies creating middleware components.

[taion]

We have two scroll management middlewares now: https://github.com/ryanflorence/react-router-restore-scroll, https://github.com/taion/react-router-scroll. Naturally, I like mine more, but we should probably have one with the union of the feature set :p

[taion]

I'm going to fold this into an updated meta issue for the upcoming 3.x release, intended as a minor update to the 2.x API.

[taion]

Tracking concrete goals and maybe-goals for v3.0.0 on #3611.