Continue adding fetch methods to the SDK

[juangm]

No description provided.

[height]

This pull request has been linked to 1 task:

• T-23563 REACT: add second batch of missing methods for fetch (unlink task)

💡Tip: Add "Close T-23563" to the pull request title or description, to a commit message, or in a comment to mark this task as "Done" when the pull request is merged.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment

Name	Status	Preview	Updated (UTC)
lens-sdk-example-web-wagmi	⬜️ Ignored (Inspect)		Jan 23, 2025 9:59am

[changeset-bot]

⚠️ No Changeset found

Latest commit: 445741e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

[cesarenaldi]

I didn't check this in detail, but wherever the request is optional, and from the example useAccountManagers() it seems so, this param should optional.

Otherwise this will only work with an awkward empty object useAccountManagers({}) if no specific args are needed.

[cesarenaldi]

I believe in the case of optional args for non-suspense signature we need to also provide a default value here:

Suggested change

	}: AccountManagersArgs & { suspense?: boolean }): SuspendableResult<Paginated<AccountManager>> {
	}: AccountManagersArgs & { suspense?: boolean } = {}): SuspendableResult<Paginated<AccountManager>> {

This is not visible from the outside, it's just needed to TS to support all signatures.