feat: add generated types for Expo Router useSegment

[marklawlor]

Why

• Add type generation for Expo Router's useSegment
• Adds code comments and renames a few internal types.
• Refactored the useSearchParams types
• Add default to Href<T>

Note that this is not a breaking change as the generated types are only present inside the users' cache and should not be committed. Next time the user starts the dev server they will get the new generated types.

Questions

@EvanBacon Given the route /(app)/note/[note]/ does useSegments return the group?

useSearchParams

This hook was a bit strange as its signature changed when you enabled types routes.

Without: useSearchParams<T extends Record<string, string>(): T
With: useSearchParams<T extends Route>(): SearchParams<T>

This PR updates the TypedRoutes version to accept either a Route or a Record. This Record is still typed checked and it must satisfy a possible SearchParams object.

For example

// This will only work if you have a [test] route somewhere in your app
const { test } = useSearchParams<{ test: string }>()

I quite like this as it allows you to cherry-pick the param that you need.

Note that this obviously doesn't do a runtime check for it maybe be correct, but its a start.

Href

Href has a default value and by default now represents all possible Hrefs. You can use the generic to reduce it down.

[EvanBacon]

Approve pending better test coverage.

[marklawlor]

Some updates

• Search params and hashs are no longer valid in the Href form. TypeScript is unable to validate if they are correct, so you much the the HrefObject notation
• External Urls are valid Href's
• The logic for OptionalCatchAllRoutePart has been added but is unused. This means CatchAll routes are currently required when using the Href version, but are optional when using HrefObject (you can supply an empty array
  • I think this is the best approach until we introduce the syntax for optional catch all routes