[Feature Request] Support undefined or null value in `searchParams`?

[Connect-a]

I think there are cases where you want to pass undefined or null to the searchParams.

type Foo = {
  a: string;
  b?: number;
};

const foo: Foo = { a: 'a' };

ky.get('https://example.com', { searchParams: foo }); 
// ↑ TS2322: Type 'undefined' is not assignable to type 'string | number | boolean'.

Is it possible to accept undefined / null values and ignore them?

[sholladay]

We could JSON.parse(JSON.stringify(searchParams)), which would remove undefined. I'm less certain about whether removing null is a good idea. It wouldn't surprise me if some backends are relying on ?foo=null.

[Connect-a]

In fact, I don't really have an image of how null is handled in the get method.
Since only strings can be passed to the query string, I think concepts such as null and undefined should be ignored.

Personally, I don't think the string "null" will be sent when the query parameter of the get method is set to null.