DO NOT MERGE: alternative state management RFC

[jonathanawesome]

Tracking issue #2904

[changeset-bot[bot]]

⚠️ No Changeset found

Latest commit: 1d360ef3bdf6c07257a75e1031c4d0c1bfabb346

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

[github-actions[bot]]

The latest changes of this PR are not available as canary, since there are no linked changesets for this PR.

[acao]

Decided not to invite y’all as proper reviewers yet because it’s still WIP but @B2o5T and @thomasheyenbrock we feel that we can rework state management in a 2.x refactor to make the rest of the planned features and plugin API easier to build, and for more intelligent & efficient component rendering - what do you think?

[acao]

@thomasheyenbrock yes this was part of the original plugin proposal in #1689 , the idea was that the plugin API should be able to support doc explorer, query history, etc as plugins!

also, @graphiql/react is still in 0.x state, so direct consumers will expect breaking changes over minor versions as per semver until we feel we have a stable API for 1.x (maybe that can be the goal for 3.0.x).