In some cases, it may be beneficial to store routes as objects instead of components.
In larger applications, routes quickly get repetitive, verbose, and repetitive. 😉
It’s a huge brick of text in the middle of your render
. It works, but it doesn’t look too good. Previous versions of React Router represented routes as objects; while that syntax is gone with React Router 4, it’s pretty easy to throw together something similar.
You probably noticed that routes tend to take the same kind of props. Let’s represent them as objects:
Using this object, you can simplify App
:
Thanks for learning with the DigitalOcean Community. Check out our offerings for compute, storage, networking, and managed databases.
While we believe that this content benefits our community, we have not yet thoroughly reviewed it. If you have any suggestions for improvements, please let us know by clicking the “report an issue“ button at the bottom of the tutorial.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!