On Wednesday, October 19, 2016 at 4:39:00 PM UTC+1, OvermindDL1 wrote: > > I've been using absinthe on the server side and I am able to control > access permissions quite well for GraphQL hosting, though I am using a > custom permission library that ties to our local LDAP server so that code > would not be generically useful to release. >
Sounds interesting. Is hooking custom permissions into graphql part of the graphql spec? Or is it some mechanism specific to absinthe that lets you do this? Also, is graphql just for fetching data? Or it also allows you to create new data on the server, or make updates to existing data? > But yes, I am a fan of GraphQL. I just expose 'functionality', not raw > tables. Many of my GraphQL calls do not map to a database table but rather > potentially multiple (or even none in some cases). > Yes, I also do not expose raw tables in the API, each entity is typically a small document tree which maps to >1 table. Also depending on what you fetch and what condition you use to filter the query results I would expect hitting >1 table to be quite common. -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
