René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"JS Client: Uri inference in invocation","articleBody":"Our invoke function in the JS client looks like this:\r\n```ts\r\n  public async invoke\u003cTData = unknown, TUri extends Uri | string = string\u003e(\r\n    options: InvokerOptions\u003cTUri\u003e\r\n  ): Promise\u003cInvokeResult\u003cTData\u003e\u003e {\r\n    return super.invoke({\r\n      ...options,\r\n      uri: Uri.from(options.uri),\r\n    });\r\n  }\r\n```\r\nThere is a problem in how the generics are defined, in which if we pass a generic for the result type, the Uri must be a string (unless its defined). For example, if we do this:\r\n```ts\r\n  const t = await client.invoke\u003cString\u003e({\r\n    uri: new Uri(\"wrap/polywrap\"),\r\n    method: \"h\"\r\n  })\r\n}\r\n```\r\nIt will complain because the `uri` is of type `Uri`, instead of `String` we should support that the default is `Uri`","author":{"url":"https://github.com/krisbitney","@type":"Person","name":"krisbitney"},"datePublished":"2023-09-14T08:05:43.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/79/javascript-client/issues/79"}