From c47464c7e51c38cdf21a9fc2db81248daee2d171 Mon Sep 17 00:00:00 2001 From: Matt Brophy Date: Wed, 6 Dec 2023 09:05:29 -0500 Subject: [PATCH] Clarify relative="path" docs --- docs/components/link.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/components/link.md b/docs/components/link.md index b32e02271c..9b415331f7 100644 --- a/docs/components/link.md +++ b/docs/components/link.md @@ -65,7 +65,7 @@ A relative `` value (that does not begin with `/`) resolves relative to ## `relative` -By default, links are relative to the route hierarchy (`relative="route"`), so `..` will go up one `Route` level. Occasionally, you may find that you have matching URL patterns that do not make sense to be nested, and you'd prefer to use relative _path_ routing. You can opt into this behavior with `relative="path"`: +By default, links are relative to the route hierarchy (`relative="route"`), so `..` will go up one `Route` level from the current contextual route. Occasionally, you may find that you have matching URL patterns that do not make sense to be nested, and you'd prefer to use relative _path_ routing from the current contextual route path. You can opt into this behavior with `relative="path"`: ```jsx // Contact and EditContact do not share additional UI layout @@ -79,7 +79,8 @@ By default, links are relative to the route hierarchy (`relative="route"`), so ` function EditContact() { // Since Contact is not a parent of EditContact we need to go up one level - // in the path, instead of one level in the Route hierarchy + // in the current contextual route path, instead of one level in the Route + // hierarchy return ( Cancel