You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The convention we have of prefixing dataset_ to dataset names is just a way of avoiding collisions on field names in graphql. An alternative (perhaps more elegant) approach would be to nest datasets under a dataset field, e.g. instead of:
The convention we have of prefixing
dataset_
to dataset names is just a way of avoiding collisions on field names in graphql. An alternative (perhaps more elegant) approach would be to nest datasets under adataset
field, e.g. instead of:We could do:
Obviously if graphql ever gets namespaces graphql/graphql-spec#163 we could use those.
The text was updated successfully, but these errors were encountered: