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

fix(GraphQL): GraphQL schema is preserved after drop_data (#5790) #5840

Merged
merged 2 commits into from
Jul 8, 2020

Conversation

abhimanyusinghgaur
Copy link
Contributor

@abhimanyusinghgaur abhimanyusinghgaur commented Jul 6, 2020

Fixes #GRAPHQL-370.

This PR makes sure that the GraphQL schema is preserved after drop_data operation. It also makes sure that the getGQLSchema GraphQL admin resolver reports empty schema after drop_all.

(cherry picked from commit 747c896)

# Conflicts:
# graphql/resolve/resolver.go


This change is Reviewable

Docs Preview: Dgraph Preview

Fixes #GRAPHQL-370.

This PR makes sure that the GraphQL schema is preserved after `drop_data` operation. It also makes sure that the `getGQLSchema` GraphQL admin resolver reports empty schema after `drop_all`.

(cherry picked from commit 747c896)

# Conflicts:
#	graphql/resolve/resolver.go
@github-actions github-actions bot added the area/graphql Issues related to GraphQL support on Dgraph. label Jul 6, 2020
…imanyu/cherry-pick4

# Conflicts:
#	graphql/resolve/resolver.go
@abhimanyusinghgaur abhimanyusinghgaur merged commit 267608e into release/v20.07 Jul 8, 2020
@abhimanyusinghgaur abhimanyusinghgaur deleted the abhimanyu/cherry-pick4 branch July 8, 2020 04:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/graphql Issues related to GraphQL support on Dgraph.
Development

Successfully merging this pull request may close these issues.

1 participant