You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
as per conversations since 2019, and a conversation with users at GraphQL Berlin meetup, it's high time we start work on a simple set of utilities to enable graphiql plugin development!
this provides some conventions and abstracts away the details to make shipping plugins more readily poasible from this repo (or from any repo)
(also, as a platform engineer, seeing all the duplicate vite config and pain for users just made me sad, vite's plugin API was designed to eliminate such complexity!)
vite plugin to abstract away config details
shared tsconfig
[x] automatically rename output to match plugin name
add docs for creating plugins
in later iterations
init script (npx create-graphiql-plugin myplugin)
validate package.json
extend vite plugin to show graphiql with plugin on vite command
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
acao
changed the title
add @graphiql/plugin-utils to simplify plugin development
add @graphiql/plugin-utils, docs to improve plugin development
Jul 8, 2023
Note: I've added a few commits to graphiql explorer plugin to this PR to fix an upstream issue, but I plan to backport them to happen independently as a bugfix, and restore copy-demo in a seperate PR
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
acao
force-pushed
the
graphiql-plugin-utils
branch
4 times, most recently
from
as per conversations since 2019, and a conversation with users at GraphQL Berlin meetup, it's high time we start work on a simple set of utilities to enable graphiql plugin development!
this provides some conventions and abstracts away the details to make shipping plugins more readily poasible from this repo (or from any repo)
(also, as a platform engineer, seeing all the duplicate vite config and pain for users just made me sad, vite's plugin API was designed to eliminate such complexity!)
[x] automatically rename output to match plugin namein later iterations
npx create-graphiql-plugin myplugin)vitecommand