-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GraphQL support #5014
GraphQL support #5014
Conversation
Codecov Report
@@ Coverage Diff @@
## master #5014 +/- ##
==========================================
+ Coverage 93.86% 94.13% +0.26%
==========================================
Files 123 148 +25
Lines 8972 9567 +595
==========================================
+ Hits 8422 9006 +584
- Misses 550 561 +11
Continue to review full report at Codecov.
|
0a5a203
to
87b4922
Compare
8c2b45e
to
142a070
Compare
@flovilmart Can you update the readme? I would like to test this out. Also how would we go about using GraphQL with the SDK's? |
That’s the beauty, no need of a SDK. It’s fully compatible with relay :) use graphqli and enjoy :) |
Oh I see |
And as for what’s left, a logIn/ signup mutation with the auth data like Facebook, Twitter etc is just what’s missing |
Really interesting, a quick question, on the Query part, has the GraphQL live mutation subscribe been integrated @flovilmart ? |
Not yet, I wanted to get the initial modeling out there, now it’s been a while. I believe subscription will be an interesting extension to it. Is it something you want to work on? |
UPDATE : the subscription system for |
https://graphql.org/blog/subscriptions-in-graphql-and-relay/ This describe subscriptions as part of the spec / language and not a particularity. As we do it with live queries, we could support a simple query based subscription model. |
@flovilmart I'm a new beginner in the world of graphQL, I need a little learning on it, then I dive into it. On the documentation side too, we're going to have to write a graphQL doc no ? |
The good thing about graphQL is that it’s self documenting. The pieces we need to document are around handling session tokens. I have a todo demo app based on relay which #justworks (I need to share it though). |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Here is the relay example forked for parse-server https://github.com/parse-community/relay-examples What is missing in the example is the login flow, acuireing a session token, which is not completely necessary but would be nice as an example to show. I'll let you guys play with it and improve it as it should |
Closing due to lack of activity |
Oh no :( this feature would have been very good to have in parse-server :/ :/ |
Would have for sure, and would have obliterated the need for client SDK’s once and for all. The code is still available on the branch for anyone to pick up and continue Sent with GitHawk |
user email verification(not needed)