Replies: 1 comment
-
I think generally we've avoided this because handles are route-specific so a single shared |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We use react-router in "data-loader" mode today and leverage the
handle
prop fromRouteObject
to define breadcrumbs.Today I have to override a lot of types to get the handle prop to be strictly defined (from it's default any) but if the library referenced a
interface Handle {}
type then I could override it using declaration merging in my application and have that type be properly consumed everywhere.Any interest in allowing this? Happy to contribute if you are open to it.
On a side note: I do fear slightly you want to move away from the
handle
prop as it's mentioned less and less in the v7 docs. I personally love it, but just want to make sure if thats the direction the library is considering then I don't want to tie our logic in to it too deeply if we can avoid it.Beta Was this translation helpful? Give feedback.
All reactions