menu
Channels
Team
Posts
Members
Info

Redirect to relative path not working

If the value of the "to" prop on a Redirect component is "baz" at "http://127.0.0.1/foo/bar"; however, it redirects to "http://127.0.0.1/baz" not "http://127.0.0.1/foo/baz", is that expected? I've seen an issue on GitHub detailing the problem, but they were closed even though…

thumbsup
0
message-simple
4

useLocation hook?

Would anyone be interested in a useLocation hook that returns the location context? I think this gives more of a declarative API versus exporting the context itself.

thumbsup
0
message-simple
5

There's an undocumented (and very useful) `openOnFocus` prop! [ComboBox]

While reading through the ComboBox source code I stumbled upon a "hidden" prop. It does exactly what is says. It opens the suggestion popover when the input is focused! I tried to replicate this functionality before, but it did not work as well. Here's a small demo:…

thumbsup
0
message-simple
0

exporting `match` util function

I think it would be useful to export the match utility function so that other parts of the app (redux reducers and side-effect middleware) can react to route changes and whatnot. What do you think?

thumbsup
0
message-simple
0

Router: A title prop to update page titles

I just made a feature proposal on GitHub to add a title prop to the children of Router that would update the page title when that component renders. I think this would add a useful accessibility feature to the API. What do you all think?

thumbsup
2
message-simple
0

passing props with redirect component

hello. is there any documentation about passing a props to Redirect component like this in react-router? if none is there a way? like a "hack" if not. I was thinking, since we're using redux so for every link ill put a action that pass the path so i can grab it from the store.

thumbsup
0
message-simple
3

Question Regarding Push/Pop state in `@reach/router`

I am developing a GatsbyJS site and thus am using @reach/router as a result. It is a great router! I have an issue while trying to implements some page transitions. I am using react-pose for the transitions. I feel it relies on a POP and a PUSH state to initiate the exit and…

thumbsup
0
message-simple
0

<Link to={Object} />

This is quite a valuable feature of react-router. Of course, I can easily implement it on my side, like this: My question is, whether something like that is welcome to be a part of Reach Router API. If it is, I'm happy to send a PR

thumbsup
0
message-simple
0

Select?

Hey @ryanflorence 👋 Firstly thanks for the effort, I've been following you for some time now and also been using quite a few of your libs. I think your goal to be a low-level accessible base-library for react here is absolutely amazing. Today the usual question of custom vs.…

thumbsup
0
message-simple
1

give me a ref instead of create a div for me via Router component

I would like to manage the elements that get created, I'd rather pass a ref into my components than have you create a div for me. Would you consider this as a feature?

thumbsup
0
message-simple
1