[bug]: Support `exactOptionalPropertyTypes`

[mrmckeb]

Description

We're using TypeScript's stricter exactOptionalPropertyTypes in our project, which is working well - however the types shipped by Algolia are not compatible with this setting.
https://www.typescriptlang.org/tsconfig/#exactOptionalPropertyTypes

I'm happy to submit a PR. The required change is to add undefined to the optional fields, for us the issue is specifically with the package @algolia/recommend -> browser.d.ts.

For example:

-    filters?: string;
-    facetFilters?: FacetFilters;
-    optionalFilters?: OptionalFilters;
-    numericFilters?: NumericFilters;
-    tagFilters?: TagFilters;
+    filters?: string | undefined;
+    facetFilters?: FacetFilters | undefined;
+    optionalFilters?: OptionalFilters | undefined;
+    numericFilters?: NumericFilters | undefined;
+    tagFilters?: TagFilters | undefined;

Client

Recommend

Version

5.25.0

Relevant log output

[Haroenv]

It makes sense, but you'll need to make the pull request in https://github.com/algolia/api-clients-automation

[mrmckeb]

It looks like this may not be possible from this issue:
OpenAPITools/openapi-generator#14793

However, we've found that we can use this to modify the type.
https://github.com/sindresorhus/type-fest/blob/main/source/undefined-on-partial-deep.d.ts

[shortcuts]

Hey, I tried enabling the option in algolia/api-clients-automation#4935, and if I understand correctly, all it takes is explicitly stating that optional properties should allow undefined, right?

I think this is an acceptable option to enable, and doesn't seem to be a breaking change in any way

[shortcuts]

You can preview the generated code here algolia/api-clients-automation@956b602

[mrmckeb]

That's great, thank you so much!