olegabu/graphiql-explorer-sql

Graphiql with explorer and minimal sql editor

graphiql-explorer-sql's Issues

Document build process

Replace default React logo and favicon

with graphql https://en.wikipedia.org/wiki/GraphQL#/media/File:GraphQL_Logo.svg

Subsriptions to update the results pane via websocket

GraphQL queries can be turned into subscriptions that update asynchronously when a query result changes. You can subscribe to get updates via websocket using cli graphqrl or in the GraphiQL GUI on Hasura's website: turn a query into a subscription and see the right results pane turn into a waiting mode and update on a change to the query result. If you do the same in our IDE you'll get an error subscriptions are not supported over HTTP, use websockets instead.
Figure out how this is done in Hasura or in GraphiQL IDE and implement.

You can test subscriptions by querying for the latest block even though they come infrequently, like so: replace query with subscription and give the next block number you expect to receive from the sequencer.

query raw_block {
  raw_block_by_pk(block_number: 267000) {
    raw
  }
}

Streamline the SQL editor style

The SQL editor pane is taken as a component from another web app with their own styles they don't fit our IDE look. Correct the styles, widths and position within the SQL pane so it looks like an integral part of the IDE.

Create a mock API for SQL editor

The SQL editor should send its requests to Hasura API or elsewhere -- they deserve a separate repo. In this repo create a minimal express API that returns dummy data in response to a GET request from the SQL editor pane. When no API endpoint specified by an env variable at build time the SQL editor will call this dummy API and will load its response into its results table. Later on this dummy API can be used as a blueprint for the real API.

Move hardcoded into env variables

We have the graphql url and queries hardcoded, move them into env variables so they can be updated at build time.

Document SQL editor