Experience Report for Feature Request What you wanted to do Read my schema. We should hide the internal predicates as they aren’t useful exposed. Also, we could expose them if we set some debug processes or dev mode. What you actually did Why that wasn’t great, with examples Users may get confused …

One example of confusion [image] Confused with the external id Users Dgraph kind:question I read the doc of it …

OMFG YES. And also we should update the schema{} query to support showing them or not. It’s annoying when you have a 2-3 page long schema and you scroll thru and suddenly <dgraph.graphql.foo>.

Yes. We should hide them. @hardik

Please hide the internal predicates

Issues Dgraph

MichelDiz (Michel Diz) March 25, 2021, 5:19pm 3

One example of confusion

Topic		Replies	Views
Schema query filtering Dgraph dgraph , priority:p2 , status:accepted , kind:feature , status:needs-specs	5	993	May 18, 2020
GraphQL on Existing Dgraph - Graphql Documentation	4	1068	September 30, 2020
Schema created by Graphql is not accessible when making graphql+- calls and vice versa Dgraph graphql , schema	5	881	August 27, 2020
Beginner question: Connecting to Dgraph directly from the front-end App Development discussion , kind:question	7	1889	November 14, 2020
Handling internal Type/Predicate Dev eng	1	681	May 27, 2020

Please hide the internal predicates

Related topics