Make it easy to expose GrapQL APIs in addition (or instead of) traditional REST API.
See https://github.com/facebook/graphql/issues/3
@raymondfeng could you please share the result of your discussion with @leebyron and what are the next steps we need to take in order to make this happen?
bajtos
All 41 comments
@leebyron You have locked facebook/graphql#3 for collaborators only. Would you mind adding a comment linking to this new issue, so that people can find the place where the discussion is continuing?
bajtos
on 27 Nov 2015
I'm interested in this too...
AshleyAitken
on 29 Nov 2015
馃憤
JohnCoppa
on 14 Jan 2016
+1 Any updates?
gaurav21r
on 25 Jan 2016
:+1:
Industrial
on 30 Jan 2016
Very interested in having graphql support
ainesophaur
on 11 Feb 2016
https://github.com/RisingStack/graffiti looks like a promisig project. If an adapter could be written between this and the Loopback model layer, then you could just use it as an express plugin.
Industrial
on 11 Feb 2016
+1
GauSim
on 11 Feb 2016
:+1:
violet-day
on 12 Feb 2016
Would love to see GraphQL support in loopback!
adanielyan
on 13 Feb 2016
+1
terehov
on 17 Feb 2016
:+1:
esco
on 17 Feb 2016
:+1:
Taik
on 17 Feb 2016
+1
Peege151
on 17 Feb 2016
+1 any updates on progress?
jordan112
on 6 Mar 2016
Love to see graphql support
dligthart
on 14 Mar 2016
+1
GauSim
on 22 Mar 2016
:+1:
PhearZero
on 23 Mar 2016
:+1:
DFranch
on 30 Mar 2016
Guys there are _reactions_ now in Github. Lets use them instead of a new comment for +1
gaurav21r
on 31 Mar 2016
:+1:
sbacem
on 12 May 2016
:+1:
jeff3yan
on 1 Jun 2016
any news about this functionality ? would be nice if is working or not in this feature.
bedomo
on 4 Jul 2016
馃憤
seefeld
on 8 Sep 2016
+1
mraak
on 9 Sep 2016
+1
marcelorl
on 12 Sep 2016
+1
romulocintra
on 15 Sep 2016
does it need a change to all datasources or a transmission layer of graphql query to json?
sshbio
on 16 Sep 2016
@shSina Transmission layer is enough. You can even resolve from existing rest end points. Wouldn't be a huge task to make something basic.
mraak
on 16 Sep 2016
@mraak I'm thinking of the way we can manage ACL inside transmission layer, we can check the request token on all requested relations before transmission and handling the errors... ,
and I should test whether it's possible to override user predefined relations scope (in json) in js dynamically to separate the effect of graphQL endpoint from REST one or not.
sshbio
on 17 Sep 2016
馃憤
kerwynrg
on 1 Oct 2016
+1
caoer
on 3 Oct 2016
馃憤馃徎
osenvosem
on 9 Oct 2016
Anyone feels like checking this and providing feedback? It is still in infancy.
https://github.com/Tallyb/loopback-graphql
Tallyb
on 15 Oct 2016
Any news on this?
thiago-soliveira
on 29 Nov 2016
any Updates?
ae1080
on 12 Apr 2017
+100000 on this
rblalock
on 3 Jul 2017
This is another option based on @Tallyb's project https://github.com/BlueEastCode/loopback-graphql-relay
beeman
on 3 Jul 2017
Has there been any progress on this?
smshuja
on 17 Jul 2017
Any progress? 馃檪
abdonrd
on 25 Dec 2017
See https://github.com/strongloop/loopback-next/issues/656 and https://github.com/strongloop/loopback4-extension-graphql
bajtos
on 5 Jan 2018
Related issues
JoeShi
路
4Comments
imasif
路
3Comments
Overdrivr
路
3Comments
greaterweb
路
4Comments
AnupDeshpande23
路
4Comments
Most helpful comment
Guys there are _reactions_ now in Github. Lets use them instead of a new comment for
+1