This might be totally on me and how I am deleting data. I have deleted Relationships that had meta edges, but those meta (RelationshipMeta) were not also deleted. So that is what is propagating the error.
So I guess this ties into my other topic:
I wasn’t thinking the orphaned data would be important and I just skipped over deleting the children. In order to delete all of them I would have to change my UI from deleting a single type by ID to now query that type by ID and get the ID of all of the children that also need deleted and then run a mutation deleting the type by ID and the children by IDs. This is what it will take to keep the UI on a GraphQL endpoint only and make a deep delete.
I guess I could remove the required field, the dilemma…
I will just remove the ! off from RelationshipMeta.forRelationship. That is the easiest fix without deep deleting children.
When has comes to slash, I should be able to use it to clean up some of the orphaned children.
What would be awesome: (I think I suggested this somewhere before too)
If the Non-nullable field ‘fieldName’ (type fieldName!) was not present in result from Dgraph. GraphQL error propagation triggered. was caught before it reached the client and it acted like a cascade instead removing any fields that were required but not present.