Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GraphQL API playground #1123

Merged
merged 13 commits into from
Jul 4, 2019
Merged

Conversation

douglasmuraoka
Copy link
Contributor

Adds the GraphQLConsole component under the API Console category, which allows users to test the parse-server GraphQL API. The component should be mounted with X-Parse-Application-Id and X-Parse-Master-Key headers, and the parse-server's GraphQL API endpoint set. It means it will be ready to execute queries/mutations as soon as it is opened.

All the information required (applicationId, masterKey and graphQLServerURL) must be defined on the ParseApp instance in order to work properly.

Parse Dashboard GraphQL Playground

@davimacedo
Copy link
Member

What happens if graphQLServerURL is not set? I wanted to make sure that either the GraphQL console will not show up or we will have a friendly message introducing GraphQL as most of the developers have not yet setup GraphQL for their projects and no errors should be displayed in this case.

@douglasmuraoka
Copy link
Contributor Author

douglasmuraoka commented Jun 27, 2019

@davimacedo I was thinking about using the EmptyState component. The same used when there are no Jobs scheduled, for instance. It will show a title, a message (which contains a link to the Parse documentation, GraphQL section), and an icon.

Something like this.
Screenshot from 2019-06-27 11-23-13

What do you think?

Copy link
Member

@davimacedo davimacedo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks pretty good. Could you please work on these 3 items?

  1. Rebase the branch
  2. In the "blank" version, the image and text is not center aligned as you can see in the picture below.

Screen Shot 2019-07-02 at 2 32 48 PM

3) In the "working" version, shouldn't we have the default header with title "GraphQL API Console" like in the "blank" version and in the REST API Console?

@davimacedo davimacedo merged commit d04b7f0 into parse-community:master Jul 4, 2019
acinader added a commit that referenced this pull request Jul 10, 2019
beiguancyc pushed a commit to beiguancyc/parse-dashboard that referenced this pull request Jul 13, 2019
* parse: (21 commits)
  Reset credentials (parse-community#1135)
  1.4.0 version bump + changelog (parse-community#1134)
  Fix: Master fails to install graphql-playground parse-community#1131 (parse-community#1133)
  Update eslint-plugin-react to the latest version 🚀 (parse-community#1122)
  Update babel7 to the latest version 🚀 (parse-community#1129)
  GraphQL API playground (parse-community#1123)
  Fix: Can't switch (dropdown list) between servers parse-community#1045 (parse-community#1125)
  Update puppeteer to the latest version 🚀 (parse-community#1124)
  Update eslint-plugin-react to the latest version 🚀 (parse-community#1120)
  Update webpack-cli to the latest version 🚀 (parse-community#1119)
  Update react-dnd to the latest version 🚀 (parse-community#1117)
  Update puppeteer to the latest version 🚀 (parse-community#1116)
  Update react-dnd to the latest version 🚀 (parse-community#1114)
  Update babel-eslint to the latest version 🚀 (parse-community#1113)
  Update react-dnd to the latest version 🚀 (parse-community#1111)
  Update react-dnd to the latest version 🚀 (parse-community#1110)
  Update package-json to the latest version 🚀 (parse-community#1108)
  Update webpack-cli to the latest version 🚀 (parse-community#1106)
  Update react-dnd to the latest version 🚀 (parse-community#1104)
  Update webpack-cli to the latest version 🚀 (parse-community#1103)
  ...

# Conflicts:
#	package-lock.json
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants