Sketch of new Request(Proxy(Request))

[jasnell]

A skech of an approach to addressing #6700

This is not quite functional yet due to a limitation with handling jsg::Objects through the lens of JSG_STRUCT... well, more limitation of handling jsg::Objects through Proxy:

  const rp = new Proxy(r, {
    get(...args) {
      return Reflect.get(...args);
    }
  });

  console.log(rp.url);  // throws

This is a different problem tho. The sketch shows how we can make new Request(Proxy(Request)) work in general.

[vicb]

@jasnell while trying to validate the fix, I noticed that the lockfile is out of date. I created #6731

However doing so breaks the build.
But the build also fails with the checkedin lockfile on mac.

[jasnell]

@vicb ... this won't work anyway until the more general issue of wrapping jsg::Object's with proxies is addressed.

[kentonv]

Instead of reproducing all this logic here, it would be nice if we could delegate to the existing RequestInit path. Only the url needs special handling.

Otherwise it's easy to forget to add new properties here.

[kentonv]

Can we possibly use RequestInit here instead of declaring a new type? It seems ugly that we'd have to extend this type later.

I guess the only problem is that RequestInit doesn't include url. Though maybe it could -- just declare it optional, and ignore it except in the proxy case?

Relately, I see you dismissed Bonk's comment pointing out that cache and encodeResponseBody are missing, but that does seem like an actual problem, no?

[jasnell]

Dismissed to reduce a small amount of noise in the discussion. Already planning to account for both of we decided that this was a worthwhile approach.