You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 5, 2019. It is now read-only.
We don't want to have to manually construct URL paths every time we write a <Link>. In the old days, React supported named routes natively, but they ditched that for dubious reasons. Fortunately however there are third party replacements, e.g. https://github.com/adamziel/react-router-named-routes, which should let us write stuff like:
Description
We don't want to have to manually construct URL paths every time we write a
<Link>
. In the old days, React supported named routes natively, but they ditched that for dubious reasons. Fortunately however there are third party replacements, e.g. https://github.com/adamziel/react-router-named-routes, which should let us write stuff like:Acceptance Criteria
This story can be considered done when the following acceptance tests
are satisfied:
Given all the
<Link>
elements in the UIWhen they need to link to some route within the app (i.e. not external links)
Then the link path should be generated dynamically rather than hardcoding assumptions about the structure of the URL path.
The text was updated successfully, but these errors were encountered: