Use existing graphql schema instead of recreating the models about modelizr HOT 7 CLOSED

I agree. It would be nice to support graphql-js's SchemaTypes - definitely something I would like to introduce in future.

from modelizr.

I've been thinking more about this, and I'm doubting the necessity of this. Modelizr is a client targeted library and in my opinion it should have models that are not glued to the server-side GraphQL schemas.

@jansenignacio Could you perhaps describe a use case that this could make sense?

from modelizr.

@julienvincent can you think of a case when you wouldn't want the client to be 'glued' to the server.

from modelizr.

Yes, most of the time the client does not want to / is not authorized to view all of the fields available on a schema.

from modelizr.

Authorization is a server-side concern.
What is the problem with having a full type specification when you only need 80%.

from modelizr.

@julienvincent after using GraphQL a bit more, I've also come to the same conclusion as you. The use case I had thought of is not really valid.

from modelizr.

@jansenignacio Thanks for your input - you might also be interested in looking at the rewrite for v1. Creating a model is now much less verbose and hopefully makes this library more user friendly.

from modelizr.