Allow RpcRequest params to be of any type, instead of requiring an array

[mcintyre94]

This provides flexibility for APIs that do not use an array of params. For example Helius' non-standard APIs expect params to be an object and don't use an array wrapper, like this:

{
    "jsonrpc": "2.0",
    "id": "text",
    "method": "getTokenAccounts",
    "params": {
        "owner": "some-address",
        "limit": 100
    }
}

This can be handled with a parametersTransformer:

const api = createRpcApi<HeliusDasApi>({
    parametersTransformer: (params) => params[0],
});

But currently this is a type error, because parametersTransformer is required to return unknown[]. This PR allows it to just return unknown so that the above is no longer a type error.

[changeset-bot]

🦋 Changeset detected

Latest commit: 78619c9

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

This PR includes changesets to release 36 packages

Name	Type
@solana/rpc-spec	Patch
@solana/accounts	Patch
@solana/rpc-api	Patch
@solana/rpc-transformers	Patch
@solana/rpc-transport-http	Patch
@solana/rpc	Patch
@solana/sysvars	Patch
@solana/web3.js-experimental	Patch
@solana/rpc-subscriptions-api	Patch
@solana/rpc-subscriptions	Patch
@solana/rpc-graphql	Patch
@solana/transaction-confirmation	Patch
@solana/addresses	Patch
@solana/assertions	Patch
@solana/codecs-core	Patch
@solana/codecs-data-structures	Patch
@solana/codecs-numbers	Patch
@solana/codecs-strings	Patch
@solana/codecs	Patch
@solana/compat	Patch
@solana/errors	Patch
@solana/fast-stable-stringify	Patch
@solana/functional	Patch
@solana/instructions	Patch
@solana/keys	Patch
@solana/options	Patch
@solana/programs	Patch
@solana/rpc-parsed-types	Patch
@solana/rpc-spec-types	Patch
@solana/rpc-subscriptions-spec	Patch
@solana/rpc-subscriptions-transport-websocket	Patch
@solana/rpc-types	Patch
@solana/signers	Patch
@solana/transaction-messages	Patch
@solana/transactions	Patch
@solana/webcrypto-ed25519-polyfill	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

[buffalojoec]

Seems fairly inconsequential, and the JSON RPC spec actually also uses objects not arrays.

[buffalojoec]

Do we still want the array enforced for input here?

[mcintyre94]

I think so, because the developer doesn't control that - it's just the input params to their function. From a JS perspective that'll always be a list, I think.

[steveluscher]

I checked the JSON-RPC 2.0 spec, and your change checks out! https://www.jsonrpc.org/specification#parameter_structures

[steveluscher]

…also uses objects not arrays.

The spec allows both.

[github-actions]

🎉 This PR is included in version 1.91.9 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[github-actions]

Because there has been no activity on this PR for 14 days since it was merged, it has been automatically locked. Please open a new issue if it requires a follow up.