Correct userLinkedAccountDisconnect requstSchema

The shape was the same, but it was using the requestParams schema, which can lead to bugs, if those are not the same in some point in the future

Author: Oksamies

packages/thunderstore-api/src/delete/userLinkedAccountDisconnect.ts

@@ -1,7 +1,7 @@
 import {
   ApiEndpointProps,
   UserLinkedAccountDisconnectRequestParams,
-  userLinkedAccountDisconnectRequestParamsSchema,
+  userLinkedAccountDisconnectRequestDataSchema,
 } from "../index";
 import { apiFetch } from "../apiFetch";
 
@@ -24,7 +24,7 @@ export function userLinkedAccountDisconnect(
       },
       useSession: true,
     },
-    requestSchema: userLinkedAccountDisconnectRequestParamsSchema,
+    requestSchema: userLinkedAccountDisconnectRequestDataSchema,
     queryParamsSchema: undefined,
     responseSchema: undefined,
   });

packages/thunderstore-api/src/schemas/requestSchemas.ts

@@ -469,6 +469,14 @@ export type UserLinkedAccountDisconnectRequestParams = z.infer<
   typeof userLinkedAccountDisconnectRequestParamsSchema
 >;
 
+export const userLinkedAccountDisconnectRequestDataSchema = z.object({
+  provider: userLinkedAccountDisconnectProvidersSchema,
+});
+
+export type UserLinkedAccountDisconnectRequestData = z.infer<
+  typeof userLinkedAccountDisconnectRequestDataSchema
+>;
+
 // TeamDetailsRequest
 export const teamDetailsRequestParamsSchema = z.object({
   team_name: z.string(),