Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Bug] Routes component’s getComponentForPath prop removed?

See original GitHub issue

The removal of getComponentForPath was not mentioned in the changelog and I can no longer find it in the source code of V7.

Animated Routes example is still using it, so it’s probably no longer working.

It would be good to amend the changelog and mention this breaking change.

Issue Analytics

State:
Created 4 years ago
Reactions:1
Comments:8 (5 by maintainers)

Top GitHub Comments

2reactions

wappsifycommented, May 14, 2019

Hey @simonunlikely et al., we have since figured out a way to implement animated routes with react-static v7. However we have switched to use react-static-plugin-react-router instead of the reach-router one that comes with the basic template of react-static.

We implemented the page transitions with react-spring, however you can use your preferred animation library.

You can find a working minimal example (based on the basic react-static example) here: https://github.com/wappsify/react-static-v7-animated-routes

Clone the repo, run yarn to install the dependencies, then yarn start to start it.

I hope this helps!

2reactions

wappsifycommented, May 6, 2019

If anybody has gotten them to work, I would also appreciate a nudge in the right direction regarding how to implement animated routes with react-static v7!