feat(@graphiql/react): migrate React context to zustand. Replace useExecutionContext with useExecutionStore hook and replace useEditorContext with useEditorStore hook

[dimaMachina]

No description provided.

[changeset-bot]

🦋 Changeset detected

Latest commit: 190130b

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

This PR includes changesets to release 6 packages

Name	Type
@graphiql/plugin-doc-explorer	Patch
@graphiql/plugin-explorer	Major
@graphiql/plugin-history	Patch
@graphiql/react	Minor
graphiql	Minor
@graphiql/plugin-code-exporter	Major

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

[github-actions]

The latest changes of this PR are available as canary in npm (based on the declared changesets):

[email protected]
@graphiql/[email protected]
@graphiql/[email protected]
@graphiql/[email protected]
@graphiql/[email protected]
@graphiql/[email protected]

[jonathanawesome]

Wow...what a load of work, well done!

Just pulled your branch down and looking through things. How do you feel about organizing the stores as such? For example, moving the execution store creation/state/actions out of execution.tsx and into a stores folder?

[dimaMachina]

Wow...what a load of work, well done!

Just pulled your branch down and looking through things. How do you feel about organizing the stores as such? For example, moving the execution store creation/state/actions out of execution.tsx and into a stores folder?

Hey Jonathan, of course, there will be reorganisation, for now I just wanted to do my changes as close as possible to the source location, to keep the git history :)

[jonathanawesome]

Looks like there's an old export from this file that's breaking (also exported here).

Perhaps we should run types:check along with the build ("build": "yarn types:check && vite build")?

[dimaMachina]

Looks like there's an old export from this file that's breaking (also exported here).

Perhaps we should run types:check along with the build ("build": "yarn types:check && vite build")?

yep, it was fixed in following up refactoring PR #3950, will fix it here too,

about types check - it would be nice to add github action to run types:check with turbo across all packages

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 63.94%. Comparing base (fdc0a4f) to head (190130b).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3946   +/-   ##
=======================================
  Coverage   63.94%   63.94%           
=======================================
  Files          35       35           
  Lines        3087     3087           
  Branches      948      950    +2     
=======================================
  Hits         1974     1974           
  Misses       1108     1108           
  Partials        5        5           

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.