Skip to content
This repository was archived by the owner on Apr 14, 2022. It is now read-only.

Add graphiql #1

Closed
Totktonada opened this issue Jan 24, 2018 · 1 comment
Closed

Add graphiql #1

Totktonada opened this issue Jan 24, 2018 · 1 comment
Assignees
Labels
enhancement New feature or request prio3 usability

Comments

@Totktonada
Copy link
Member

No description provided.

@Totktonada Totktonada added prio3 enhancement New feature or request labels Jan 26, 2018
@SudoBobo SudoBobo self-assigned this Mar 19, 2018
@Totktonada
Copy link
Member Author

It worth to make 'http' module optional dependency (consider utils.optional_require) and give meaningful error when the module does not exist and a serve method was invoked.

SudoBobo added a commit that referenced this issue Apr 16, 2018
features; now it is possible to use commands like
require('graphql').execute(...) or .start_server() with no manual creating
of graphql instance; close #1
SudoBobo added a commit that referenced this issue Apr 16, 2018
features; now it is possible to use commands like
require('graphql').execute(...) or .start_server() with no manual creating
of graphql instance; close #1
SudoBobo added a commit that referenced this issue Apr 17, 2018
features; now it is possible to use commands like
require('graphql').execute(...) or .start_server() with no manual creating
of graphql instance; close #1
SudoBobo added a commit that referenced this issue Apr 17, 2018
features

Now it is possible to use commands like
require('graphql').execute(...) or .start_server() with no manual creating
of graphql instance; close #1
SudoBobo added a commit that referenced this issue Apr 17, 2018
features

Now it is possible to use commands like
require('graphql').execute(...) or .start_server() with no manual creating
of graphql instance; close #1
SudoBobo added a commit that referenced this issue Apr 17, 2018
features

Now it is possible to use commands like
require('graphql').execute(...) or .start_server() with no manual creating
of graphql instance; close #1
SudoBobo added a commit that referenced this issue Apr 20, 2018
features

Now it is possible to use commands like
require('graphql').execute(...) or .start_server() with no manual creating
of graphql instance; close #1
SudoBobo added a commit that referenced this issue Apr 20, 2018
features

Now it is possible to use commands like
require('graphql').execute(...) or .start_server() with no manual creating
of graphql instance; close #1
SudoBobo added a commit that referenced this issue Apr 20, 2018
features

Now it is possible to use commands like
require('graphql').execute(...) or .start_server() with no manual creating
of graphql instance; close #1
SudoBobo added a commit that referenced this issue Apr 20, 2018
features

Now it is possible to use commands like
require('graphql').execute(...) or .start_server() with no manual creating
of graphql instance; close #1; changes in gql_compile is related to #16 and #50.
SudoBobo added a commit that referenced this issue Apr 20, 2018
features

Now it is possible to use commands like
require('graphql').execute(...) or .start_server() with no manual creating
of graphql instance; close #1; changes in gql_compile is related to #16 and #50.
SudoBobo added a commit that referenced this issue Apr 20, 2018
features

Now it is possible to use commands like
require('graphql').execute(...) or .start_server() with no manual creating
of graphql instance; close #1; changes in gql_compile is related to #16 and #50.
SudoBobo added a commit that referenced this issue Apr 20, 2018
features

Now it is possible to use commands like
require('graphql').execute(...) or .start_server() with no manual creating
of graphql instance; close #1; changes in gql_compile is related to #16 and #50.
SudoBobo added a commit that referenced this issue Jul 27, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request prio3 usability
Projects
None yet
Development

No branches or pull requests

2 participants