Dear @graphql people,
I’m sure you have higher priorities currently, but I have the feeling that discuss.dgraph.io is currently a little bit neglected. Before the 21.03. release the experience here was really smooth and usually I got fast answers for my questions/issues/bug-reports but this seems to have changed somehow. I wonder what is the reason?
I have a huge list of unresolved issues which are important to us as a company for adopting dgraph as our database. Let me just list them here so they won’t fade into obscurity:
- Support GroupBy query
- [Bug] StringHashFilter of update mutation does not work correctly
- Sorting Primitive List-Fields
- Allow filtering on types that implement interface
- Default values on input types
- Allow filtering on __typename
- Bundle mutations and rollback in case of error
- Custom names for CRUD-Operations
- Schema migration default values for fields
- Composite @id fields
- Atomic Field Operations
- Can we have support for file-uploads and downloads?
- @auth Rules: Check if token is valid
- [Bug] Deleting interfaces is breaking inverse relationships
- Can't add Interface-Childs with addParent(...) mutation
- ListBackups since timestamp is null
- How to delete Backups?
- Cannot Clear List with GraphQL - Dgraph execution failed because Got unsupported type for list
Currently most important for me:
- Subscriptions Lambda Field Resolver
- Dgraph-Lambda Feature Priority
- Lambda Field Resolvers: Add fields from complex childs
- Add-webhook on deep mutations
- Subscribe only to updates
- Add Node Predicates to Lambda Delete Webhook
Thank you