🙂

Damn

We really need automatic docs updates

Something I will look into

No worries!

so once I call subscribe

still not sure how to get a return result on it

It returns an observable, so you call subscribe again with an observer which is the thing that has a "next" method

Subscriptions return multiple results so a promise isn't appropriate

ahhhh

so next will return a result?

how can i get just the latest value that came in

That's something you can do at the moment

Could be useful though!

We see subscriptions as more of an event source than an updating bit of data

Okay so how do i ever extract the data from the observable

And understood on the event source, but often in real-time apps the client just cares about the last thing that came in

ie use subscription as guaranteed synch between client and server

synch of model **

If you want the last thing that came in if there's nothing new when you subscribe, then what you want is a BehaviorSubject right?

It will pass out the last value it has even if there's not something new... this is all on subscription to the observable. @theraccoun @sashko

At least that's how I have my services setup to run in my Angular app. 😛

Yeah if you wrap the observable in RxJS you can get that

Just got this error:

503 (Service Unavailable: Back-end server is at capacity)

is it a better idea to split out attributes into multiple 1:1 relations so that i can have finer mutation callback control and permission or to keep it all as attributes in the same model? Will there be performance/optimization issues in either case? the tutorials seem to use a lot of 1:1 relations, which i thought wasn’t good design unless for physical db reasons. Whats the best criteria when deciding to use a 1:1 relation?

@sajmil @howiej @willx @huggybearikf @nil.panes @samisammour @joeray welcome all to our slack! graphcool 🚀

Is it possible to have role based permissions, or is there a workaround for some functionality like this?

it is possible to get the data associated to the current logged user? I mean in a query, not passing a variable or a filter, it feels insecure

Question for the pros here: I need to call a REST API from my client. I would rather not have REST+GraphQL in the same client, so I'm looking for options. I don't see a way to do custom integrations in Graph.cool yet, so the only option I can think of is: A) Create an object, such as APIRequest from the client, and subscribe to it, B) Add a Mutation Callback that calls my server/lambda anytime an APIRequest is created, then performs the request and update the APIRequest object with status/results, C) The client that is subscribed to this request will then get the update pushed and know the results of the request etc. -- Has anyone solved this issue for themselves yet? Does this approach even sound reasonable? Has anyone tried something like this? Trying to do stuff like integrate BrainTree or other backend REST based services that require a round-trip. Thanks!

Hey there React Native developers! ⚛️ Have you already checked out React Native Express? There’s now a GraphQL section as well: http://www.reactnativeexpress.com/graphql