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 …

Please hide the internal predicates

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	949	May 18, 2020
GraphQL on Existing Dgraph - Graphql Documentation	4	1050	September 30, 2020
Schema created by Graphql is not accessible when making graphql+- calls and vice versa Dgraph graphql , schema	5	827	August 27, 2020
Beginner question: Connecting to Dgraph directly from the front-end App Development discussion , kind:question	7	1873	November 14, 2020
Handling internal Type/Predicate Dev eng	1	674	May 27, 2020