![Add optional path segment support to useMatch/matchPath · remix-run react- router · Discussion #9862 · GitHub Add optional path segment support to useMatch/matchPath · remix-run react- router · Discussion #9862 · GitHub](https://user-images.githubusercontent.com/96213/209980565-9cd5503b-4bbd-4bfd-a6cf-89d1530b173b.png)
Add optional path segment support to useMatch/matchPath · remix-run react- router · Discussion #9862 · GitHub
![reactjs - How to access routeProps (history, match, location) from a route-rendered component using react-router-dom in Typescript? - Stack Overflow reactjs - How to access routeProps (history, match, location) from a route-rendered component using react-router-dom in Typescript? - Stack Overflow](https://i.stack.imgur.com/6Y8T9.png)
reactjs - How to access routeProps (history, match, location) from a route-rendered component using react-router-dom in Typescript? - Stack Overflow
Bug]: useMatches stops returning matches when it encounters a wildcard route · Issue #8903 · remix-run/react-router · GitHub
![Data in Your Hands: How to Leverage useMatches() for Dynamic Remix Apps! | by Tam Ectosphere | Medium Data in Your Hands: How to Leverage useMatches() for Dynamic Remix Apps! | by Tam Ectosphere | Medium](https://miro.medium.com/v2/resize:fit:1358/1*NFY2Q492Ouu0UPcIIGKliA.png)