Graphql-engine: Changing a field from nullable to not nullable doesn't update the graphql schema

Created on 1 May 2019  路  3Comments  路  Source: hasura/graphql-engine

Steps to reproduce:

using the console:

  1. create table with nullable bool column
  2. update column to be NOT NULL

the docs show Boolean instead of Boolean!.

Is this by design to stop breaking changes or is it a bug?

server quickfix bug

All 3 comments

Related issue: #2096

I can replicate this. We're fixing this soon.
@anisjonischkeit as a current workaround, you can reload the metadata from /metadata/actions ( the settings icon that you can see on the top right of the console) for rebuilding your GraphQL schema

cc: @rakeshkky

Wow, that was quick. Thanks everyone!

Was this page helpful?
0 / 5 - 0 ratings