Open bigfish24 opened 6 years ago
I don't think these API would benefit from being GraphQL endpoints. They could be regular REST api.
I see, perhaps this does imply having a Realm client that includes these and GraphQL would be nice?
We could but I wonder if it makes sense to bundle them in the same module. I don't imagine you'd want to include this functionality in a user facing app. So probably it makes more sense to capsulate them in different packages, e.g. realm-auth (base package for logging users in), real-graphql, and realm-admin-client (or something). Then you can only get the api surface that makes sense for your use case.
Ooh I like that idea!
The original ROS REST data access API proposal included APIs to create a Realm (of which you need mutation support to edit the schema) but also to delete a Realm. We have a delete Realm REST API already (which is poorly documented), but could also be integrated?