(fix) - use Record over object type for subscription operation variables

[enisdenjo]

As suggested by TS and recommended ESLint rules - don't use object as a type. The object type is currently hard to use (see this issue).

This also solves the type compatibility for graphql-ws where you can use the lib in TS as you would in plain ol' JS like in #1118.

Previously, because of this object type, you have to do this:

...
subscriptionExchange({
  forwardSubscription({ query, variables }) {
    return {
      subscribe: (sink) => {
        const dispose = wsClient.subscribe(
          {
            query,
            variables: variables as Record<string, unknown>, // 😞
          },
          sink,
        );

        return {
          unsubscribe: dispose,
        };
      },
    };
  },
}),
...

[changeset-bot]

🦋 Changeset detected

Latest commit: d3c43a8

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@urql/core	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[JoviDeCroock]

This looks good to me! Would you mind running yarn changeset, marking this as a patch for core and adding a little explainer as to why this change is needed?

changesets are our way to automatically generate changelogs.

[enisdenjo]

Awesome! Is this what you had in mind?

[JoviDeCroock]

That looks great @enisdenjo, thank you!