Workaround incorrect input schema

[JustusNBB]

The following snippet from a legacy Swagger JSON schema gives me headaches, I am looking for a quick&dirty workaround to monkeypatch the input schema, so the generated SDK will actually allow me to pass an array to the (thanfully deprecated) endpoint, until the new API (with better schema) is ready...

"/products": {
            "get": {
                "summary": "Returns information about multiple products. At least one search parameter is required.",
                "parameters": [
                    {
                        "name": "omsIds",
                        "in": "query",
                        "description": "Array of OMS IDs of the products to retrieve",
                        "required": false,
                        "type": "string" // <-- NOT AN ARRAY TYPE, BUT NEEDS TO BE
                    },

// resulting type
export type QuerySearchResultViewArgs = {
  omsIds?: InputMaybe<Scalars['String']>;
  // [...]
};

The old endpoint is replaced by a wrapper which does not support querying with a simple scalar string as omsIds anymore, and won't support this incorrect schema. I need to query with omsIds[]=<ID> instead of omsIds=<ID> (if I am just querying one ID or more does not matter).

So the correct resulting type I want is:

// correct with array:
export type QuerySearchResultViewArgs = {
  omsIds?: InputMaybe<Array<Scalars['String']>>;
  // [...]
};

What's the easiest path to achieve this? Ideas:

• replace inbound schema
  • statically as a whole new source
  • surgically as a middleware patching the schema snippet on request
• tinker with generated mesh files

[ardatan]

That's not possible. You should pass the fixed schema.

[JustusNBB]

What is not possible? You mean anything else but using a static source schema?

[ardatan]

It is not possible to change the input schema in Mesh. You should download the schema and fix then pass it to Mesh.

[JustusNBB]

So I can either use a local static source of the schema, or I can create a proxy endpoint to do the schema fixing for me, anycase I have to fix the issue upstream before Mesh starts introspecting the schema.