FAQ: Learn React Router v6 - [2022 Audit] Nested Routes

This community-built FAQ covers the “[2022 Audit] Nested Routes” exercise from the lesson “Learn React Router v6”.

Paths and Courses
This exercise can be found in the following Codecademy content:

React Router
Learn React Router v6

FAQs on the exercise [2022 Audit] Nested Routes

There are currently no frequently asked questions associated with this exercise – that’s where you come in! You can contribute to this section by offering your own questions, answers, or clarifications on this exercise. Ask or answer a question by clicking reply (reply) below.

If you’ve had an “aha” moment about the concepts, formatting, syntax, or anything else with this exercise, consider sharing those insights! Teaching others and answering their questions is one of the best ways to learn and stay sharp.

Join the Discussion. Help a fellow learner on their journey.

Ask or answer a question about this exercise by clicking reply (reply) below!
You can also find further discussion and get answers to your questions over in Language Help.

Agree with a comment or answer? Like (like) to up-vote the contribution!

Need broader help or resources? Head to Language Help and Tips and Resources. If you are wanting feedback or inspiration for a project, check out Projects.

Looking for motivation to keep learning? Join our wider discussions in Community

Learn more about how to use this guide.

Found a bug? Report it online, or post in Bug Reporting

Have a question about your account or billing? Reach out to our customer support team!

None of the above? Find out where to ask other questions here!

The code breaks after putting in the nested ‘profile’ route. I can no longer see the name I used to sign in on the profile page.

1 Like

It appears that things are fixed when you carry on to part 10, useNavigate.

1 Like

I don’t understand the use of closing tags in the example code. Specifically, why do we write /> after the children’s Route Tags even though the opening tag was already closed? Is this a typo?

/* imports ... */
const router = createBrowserRouter(createRoutesFromElement(
  <Route path='/about' element={ <About/> }> {/* About renders if path starts with /about */}
    <Route index element={ <IndexComponent/> }>  />  {/* Will render when the path is /about */}
    <Route path='secret' element={ <Secret/> }>  />  {/* Will render when the path is /about/secret */}
  </Route> 
));
1 Like

Hello guys, I was wondering if you could have multiple outlets in a component to render hidden content, how would you code this?

Hello,
Why do we need to add “:” before the name “:name” in the path of the categories’ component?

const router = /* Wrap this Root Route to create Router here */ createBrowserRouter(createRoutesFromElements( <Route path="/" element={ <Root />}>{} <Route path="about" element={ <About />}/>{} <Route path="sign-up" element={<SignUp/>}/>{} <Route path ="articles" element={<Articles />}/>{} <Route path ="articles/:title" element={<Article />}/>{} <Route path="authors/:name" element={<Author/>} />{} <Route path="categories" element= {<Categories />} >{} <Route path=":name" element = {< Category/>} />{} </Route> <Route path="profile" element={<Profile />}>{} <Route path="edit" element={ <EditProfileForm />}/> </Route> </Route>));

The page on Dynamic Routes should help with understanding this.

1 Like

It didn’t work for me. I got to part 10 and the sign up part is missing