Skip to content
This repository has been archived by the owner on Nov 8, 2021. It is now read-only.

Add mutation support for schema editing #20

Open
bigfish24 opened this issue Dec 8, 2017 · 5 comments
Open

Add mutation support for schema editing #20

bigfish24 opened this issue Dec 8, 2017 · 5 comments

Comments

@bigfish24
Copy link
Contributor

This should be limited to admin users but should support:

  1. Creating new classes
  2. Added new properties to a class (additive only for synced Realms)
@nirinchev
Copy link
Member

Similarly to the create/delete api, I think this would be better off as a regular REST API - there's no apparent benefit from using GraphQL for it. Or am I missing a use case?

@bigfish24
Copy link
Contributor Author

Yeah that's true, I guess I am coming at it from the original desire to have the requirements on the data access APIs, of which this GraphQL API subsumed that work. Having a coherent client API experience would be nice.

@kraenhansen
Copy link
Member

Was this fixed or what seems to be the best work-around for now?

@kraenhansen
Copy link
Member

On the discussion of REST vs GraphQL I would say its simpler to have a single way of accessing and mutating data, so if there is no technical limitiation to having it all be GraphQL based it would most probably simplify the interface from an API consumers point of view.

@nirinchev
Copy link
Member

No, this was never prioritized.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants