<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Routing on pavsaund.com</title><link>https://www.pavsaund.com/tags/routing/</link><description>Recent content in Routing on pavsaund.com</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Sat, 26 Feb 2022 23:22:36 +0000</lastBuildDate><atom:link href="https://www.pavsaund.com/tags/routing/index.xml" rel="self" type="application/rss+xml"/><item><title>Build dynamic breadcrumb routes and child routes with matchPath in React Router v6</title><link>https://www.pavsaund.com/post/2022-02-23-dynamic-breadcrumbs-and-routes-with-react-router/</link><pubDate>Sat, 26 Feb 2022 23:22:36 +0000</pubDate><guid>https://www.pavsaund.com/post/2022-02-23-dynamic-breadcrumbs-and-routes-with-react-router/</guid><description>When faced with a challenge of implementing breadcrumbs for a business critical application recently I went down a rabbit hole of trying to understand the semantics of react-router and finding a good way of building a dynamic breadcrumb component that didn&amp;rsquo;t break every time a route was added or changed. Let alone need to implement a custom route for every new page. In this post I go into what I ended up with as a routing model that supports dynamic breadcrumbs</description></item></channel></rss>