olegilyenko / graphql-toolbox Goto Github PK

View Code? Open in Web Editor NEW

34.0 4.0 7.0 184 KB

GraphQL Toolbox - a set of GraphQL tools to help with GraphQL server and client development.

Home Page: http://toolbox.sangria-graphql.org

License: Other

Scala 30.30% JavaScript 52.12% CSS 10.85% HTML 6.74%

graphql-toolbox's Introduction

GraphQL Toolbox

A set of GraphQL tools to help with GraphQL server and client development.

Getting Started

The prerequisites are SBT, Java 8, npm.

In order to run the server locally you need to execute following commands:

$ npm install
$ sbt run

This will run the Play app in a dev mode which means that it will pick up all of the changes to a source code (this also includes resources managed by webpack).

graphql-toolbox's People

Contributors

Stargazers

Watchers

Forkers

rzachariah tlvenn ukasiu thisismana hossman333 more-free strogo

graphql-toolbox's Issues

Weird introspection query

When I just load graphiql interface (same behaviour in incognito mode), it immediately sends introspection query:

For input query as follows:

query($name: String!) {
  nameResolver(names: [$name]) {
    total
  }
}

variables:
{
  "name": "Ctenidium molluscum var. compactum"
}

it sends query, and then in second that introspection query, that actually overlaps the result.

Proxy demo doesn't work

http://toolbox.sangria-graphql.org/proxy

Provide bootstrap graphiql entry point

Right now, GraphiQL is completely self configured and bootstrapped which works great for Sangria purpose but kinda limit how it can be used outside of it.

It would be nice to introduce a bootstrapGraphiQL function that can be called from the html template. Such function should take the defaultUrl param and be passed to AppConfig.

Additionally, it would be nice to support the following optional params to configure the first tab if there is no previous state:

query
variables
response

Release as (possibly multiple) npm module(s)

To me it seems, like most of the features of toolbox are not strictly tied to scala/sbt and could be released as npm modules individually. What I'm thinking about is basically separating the js features listed on the toolbox page, and pull them in individually in this repo:

Enhanced GraphiQL - I think this would be the most crucial part to release separately. This contains features that most people who start using GraphQL need (regardless of the backend implementation) but most likely will never make it to the official GraphiQL repo considering the attitude there to keep the repo as small and protocol independent as possible. Separating this (probably putting it into its own repo under a more discoverable name) would probably (drastically) increase it's usage and popularity among node users, since looking at the issues in the GraphiQL repo, everybody comes up with half baked solutions to enable headers, tabs, etc. For me it was pure luck finding it on the second or third google page (searching for the mentioned features) being mentioned in one of @OlegIlyenko s twitter post, and oh boy am I happy I did find it. It would also make it much easier to expose the module on a cdn - #3 - using a prepublish hook or the likes.
Formatter - didn't really spend time figuring out if it's another js component doing the heavy lifting in terms of formatting, or a scala component exposed through an http endpoint. If it's the former, it would also fit nicely as a standalone npm module.
Proxy - honestly I have no idea what this does, since I didn't have any use for it yet. But again, if it's something that is implemented on the js side, then with a bit more explanation of the feature it could be it's separate module.

Now this doesn't mean splitting toolbox into multiple repos, if a mono-repo is preferred, lerna can help out in this field.

persist current state in the local storage

/format and /proxy don't do it at the moment

Publish advanced graphiql to jsdelivr

Hi,

Great work on improving on top of GraphiQL !

I was wondering if you could publish your advanced version of GraphiQL to cdnjs (similarly to how the original GraphiQL app is published there already) so that other projects could easily embed and serve it ?

Thanks a lot in advance.

Using the toolbox

Hi there,

I have a node express GraphQL server. So far I've been enabling GraphiQL directly in the express web server. I'd like to add header based authentication to my GraphQL server. That's easy enough, and I've done that, but it introduces a problem for my web IDE experience. GraphiQL doesn't natively provide a way to add headers to requests.

I thought graphql-toolbox might be a good solution for me. I noticed that graphql-toolbox allows users to provider custom headers. If I can point a graphql-toolbox server at my graphql endpoint, I will be in business.

This doesn't seem to work for me, though. I updated the defaultUrl to point to my internal graphQL server.

defaultUrl: "https://castle.ezesoftcloud.com/api/referencedata/v2/graphql",

Then I stood up a GraphQL Toolbox server with this config.

GraphQL Toolbox starts with this default URL, but it hangs loading the documentation (I guess it's trying to do introspection queries and failing).

Is my use case something that the graphql-toolbox is intended to facilitate? If so, any ideas what I'm doing wrong?

Thanks!

Docs button offscreen when screen is too small

On some laptops you can't get to the documentation. Here's a screenshot showing the issue:

I poked around for a bit but my CSS chops aren't really chops anymore.

Ability to expand and collapse the Graphiql config

setting xhr withCredentials to false

How do I do this on the graphiql client?

Abbreviate headers

This is graphiql related, hope it's still the right repo for it.

When you have a very long header, it pushes out the controls next to it, making them hard to reach (you can't actually I had to inspect the source and delete the labels contents):

I think it would be nice to abbreviate the headers text to a reasonable size (like 50 chars or so) to avoid this problem

Schema-stitching

Not sure whether this would belong here or in the main Sangria repo, but the question is if there are plans to bring schema-stitching functionality? Would really help integrating different backends as they move from REST to GraphQL

Recommend Projects

React

A declarative, efficient, and flexible JavaScript library for building user interfaces.
Vue.js

🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript

TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
TensorFlow

An Open Source Machine Learning Framework for Everyone
Django

The Web framework for perfectionists with deadlines.
Laravel

A PHP framework for web artisans
D3

Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

javascript

JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
web

Some thing interesting about web. New door for the world.
server

A server is a program made to process requests and deliver data to clients.
Machine learning

Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Visualization

Some thing interesting about visualization, use data art
Game

Some thing interesting about game, make everyone happy.

Recommend Org

Facebook

We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft

Open source projects and samples from Microsoft.
Google

Google ❤️ Open Source for everyone.
Alibaba

Alibaba Open Source for everyone
D3

Data-Driven Documents codes.
Tencent

China tencent open source team.