react provider 5

[turbocrime]

example query hooks pending other react PRs

things like this could be exported from the react package as hooks for consumers

we should

1. decide if that's a good idea
2. identify appropriate data for which to provide prewritten queriers
3. don't make queriers that are very thin (exported queriers should provide actual benefit. use-assets and use-assets-metadata are probably not appropriate)
4. (2) and (3) probably mean, queriers should be multi-endpoint requests that manipulate data. but then we need to worry about defining good interfaces/types for returned data.
5. examine the possibility of using or encouraging consumers to use connect-query instead
6. examine the possibility of doing upstream work on connect-query to add stream support, obviating this entire class of work

[changeset-bot]

⚠️ No Changeset found

Latest commit: 5f6a960

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

[VanishMax]

@turbocrime could you rebase this?

[turbocrime]

rebased. keep in mind these are example queriers, not intended to merge yet