feat: experimental support for nested route objects within components #69
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
experimental support for #62
this seems to work... but I'm not super happy with it because, well...
route.element?.type()?.props?.value?.matches[0]?.route?.children[0]?.breadcrumb
A lot of testing will be needed to make sure it doesn't cause any odd side-effects... at the end of the day, this might be a feature request for
react-router-dom
to provide some kind of way to get the entire route config context.