Rejections set document title

[stackoverfloweth]

this PR adds the setTitle paradigm to rejections that mostly mirrors how routes can set document.title.

const rejection = createRejection(...)

rejection.setTitle(() => 'My Title')

unlike route, rejection doesn't have title: Promise<string | undefined> because there's no good point to convert that from getRoute() to an executed promise. Route does this when it gets translated from Route to ResolvedRoute, but we don't have the concept of ResolvedRejection.

the arguments are also different. Rejection setTitle callback is given only SetRejectionTitleContext , which looks like

export type SetRejectionTitleContext = {
  to: ResolvedRoute | null,
  from: ResolvedRoute | null,
}

Note that to and from are only populated when the rejection happens as part of navigation. If the rejection is the result of router.reject(...), then both to and from will be null.

[netlify]

✅ Deploy Preview for kitbag-router ready!

Name	Link
🔨 Latest commit	6eed9ab
🔍 Latest deploy log	https://app.netlify.com/projects/kitbag-router/deploys/69c1470814a8ca000724d12b
😎 Deploy Preview	https://deploy-preview-743--kitbag-router.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[pleek91]

I'm surprised to see from being passed here but not used for the route version. IMO we might want to standardize this around calling getTitle on both rather than using to.title and rejection.getTitle. just for consistency.

Also I think we should separate out the logic for determining what the title should be and setting the document title. This utility is doing double duty.

[stackoverfloweth]

I've pivoted this PR quite a bit, I don't think this still applies but I'll leave it open for you to make that call