Rob Dooh

I have the same general question - how should one introduce authorization (different fields available to different users/roles)? I admit haven't gone through the spec with this in mind though,...

Point taken re: scope of library/spec. Might try dynamically generating the type schema.

@KyleAMathews No argument that this is a feature that a full server would need to implement (and that I would love to have in my hands right now). My rough...

@tristanz, probably there are many cases where allowing users to see the full schema isn't a problem, even if their access will be limited to a subset upon making requests...

Might be going out of scope here - maybe limiting introspection etc is outside of Graph-JS's core mandate, but it's a problem worth addressing elsewhere...

Thanks @leebyron and @tristanz for the food for thought. What I'm hearing then about the vision for how a schema grows is that this is usually an append-only situation, where...

Thanks for taking the time to pull me out of the rabbit hole @leebyron. In addition to your many practical points, dynamic generation would also wind up duplicating some existing...

I guess it depends on whether this is framed as a question of differing internal vs external needs, or different classes of external needs. If you're supporting public introspection, but...

Hi @smolinari - here's my definitely unauthoritative take.. ### Data-level vs Field-level I think of GraphQL as a way to present underlying data in a graph-like manner regardless of how...

Interesting - have toyed with the idea of a gui for quickly mapping out relationships... not so much for maintaining an ongoing large app so much as quickly scaffolding out...