Optional Methods on Request Class?

[michaelmerrill]

Why are all the methods on the Request class optional? Is there a recommended approach for getting rid of this typescript error (other than a non-null assertion)?

router.post('/todos', async request => {
  const content = await request.json() // Cannot invoke an object which is possibly 'undefined'.

  return new Response('Creating Todo: ' + JSON.stringify(content))
})

[kwhitley]

All are optional because itty intentionally does not require a true Request object... merely an object two properties { method, url }. Our TS contributors added the optional signatures for code-hinting.

We'll investigate this, and if you find a solution, please share it!

[michaelmerrill]

Right now I'm just extending the Request type and setting json myself. I think this is probably ok.

interface MyRequest extends Request {
  json: () => Promise<unknown>;
}