Be sure to re-run generator after upgrading
* perf: get lazy? do less?, generate more
* feat: add support for objects for children at runtime
- add type tests for objects with children
- add runtime support for objects with children
- add runtime tests for objects with children
* perf: apply similar optimisations for merging for code based
* perf: improve performance of LinkProps when passed to `Link`
* exmaples: add to large based file examples search, params and context
* docs: add TS performance recommendations to docs
* fix: remove route groups from id
* examples: update linkprops examples
* docs: update docs based on comments
* chore: remove export of `LinkComponentProps`
* chore: clean up PR
---------
Co-authored-by: Lachlan Collins <1667261+lachlancollins@users.noreply.github.com>
* test: tests for layouts without an underscore id
* test: correct the tests here
* fix: dont use the removeLayoutSegments and rework how this works
* chore: remove `@typescript-eslint/no-unnecessary-type-assertion` from router.ts
* chore: nuke the `removeLayoutSegments` function
* chore: stop eslint from freaking out
Apparently React.lazy will always suspend, even if the component is synchronously available. Makes sense, but this is annoying when used with our code-splitting paradigm. Since we preload the underlying components and even do our own top-level transition suspense for these components, it doesn't make sense to cause a React suspense boundary to suspend even if we have surely preloaded the component.
With this fix, if the component has been preloaded, it will synchronously render, otherwise it will suspend until it's been loaded.
* test(react-router): what is expected to happen
* test: .
* chore(react-router): add util for stripping out the layout identifier segments from a path
* fix(react-router): stripping out the layout identifiers segments when matching the fromRoute
* chore: .
* test: better descriptions as to whats happenning
* test(react-router): removeLayoutSegments helper
* chore: too many `"`