Pattern for Next.js path strings (App Router)
Does anyone have a good strategy for handling the paths to different pages in next? I'm using the app router but I moved some files around which adjusted the url paths for all the pages, and now I'm paranoid that I have dangling hrefs and router.push-es pointing to the old paths.
Makes me think there has to be a better way to manage the strings of where things are routed.
Long ago in my Ruby on Rails days they had amazing path helpers where you would never link or reference any path directly you would call a helper that would generate the path string and that way you never had to worry about linking to old paths.
Anyways, anyone know a good way of handling this in next+app router? Maybe there's something obvious I'm missing.
Makes me think there has to be a better way to manage the strings of where things are routed.
Long ago in my Ruby on Rails days they had amazing path helpers where you would never link or reference any path directly you would call a helper that would generate the path string and that way you never had to worry about linking to old paths.
Anyways, anyone know a good way of handling this in next+app router? Maybe there's something obvious I'm missing.
