Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

GraphQL transport #1841

Closed
bajtos opened this issue Nov 27, 2015 · 41 comments
Closed

GraphQL transport #1841

bajtos opened this issue Nov 27, 2015 · 41 comments

Comments

@bajtos
Copy link
Member

bajtos commented Nov 27, 2015

Make it easy to expose GrapQL APIs in addition (or instead of) traditional REST API.

See graphql/graphql-spec#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
Copy link
Member Author

bajtos commented Nov 27, 2015

@leebyron You have locked graphql/graphql-spec#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?

@AshleyAitken
Copy link

I'm interested in this too...

@JohnCoppa
Copy link

👍

@gaurav21r
Copy link

+1 Any updates?

@Industrial
Copy link

👍

@ainesophaur
Copy link

Very interested in having graphql support

@Industrial
Copy link

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.

@GauSim
Copy link

GauSim commented Feb 11, 2016

+1

1 similar comment
@violet-day
Copy link

👍

@adanielyan
Copy link

Would love to see GraphQL support in loopback!

@terehov
Copy link

terehov commented Feb 17, 2016

+1

3 similar comments
@esco
Copy link
Contributor

esco commented Feb 17, 2016

👍

@Taik
Copy link

Taik commented Feb 17, 2016

👍

@Peege151
Copy link

+1

@jordan112
Copy link

+1 any updates on progress?

@dligthart
Copy link

Love to see graphql support

@GauSim
Copy link

GauSim commented Mar 22, 2016

+1

2 similar comments
@PhearZero
Copy link

👍

@DFranch
Copy link

DFranch commented Mar 30, 2016

👍

@gaurav21r
Copy link

Guys there are reactions now in Github. Lets use them instead of a new comment for +1

@sbacem
Copy link

sbacem commented May 12, 2016

👍

1 similar comment
@jeff3yan
Copy link

jeff3yan commented Jun 1, 2016

👍

@bedomo
Copy link

bedomo commented Jul 4, 2016

any news about this functionality ? would be nice if is working or not in this feature.

@seefeld
Copy link

seefeld commented Sep 8, 2016

👍

3 similar comments
@mraak
Copy link

mraak commented Sep 9, 2016

+1

@marcelorl
Copy link

+1

@romulocintra
Copy link

+1

@sshbio
Copy link

sshbio commented Sep 16, 2016

does it need a change to all datasources or a transmission layer of graphql query to json?

@mraak
Copy link

mraak commented Sep 16, 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.

@sshbio
Copy link

sshbio commented Sep 17, 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.

@kerwynrg
Copy link

kerwynrg commented Oct 1, 2016

👍

2 similar comments
@caoer
Copy link

caoer commented Oct 3, 2016

+1

@osenvosem
Copy link

👍🏻

@Tallyb
Copy link

Tallyb commented Oct 15, 2016

Anyone feels like checking this and providing feedback? It is still in infancy.
https://github.com/Tallyb/loopback-graphql

@thiago-soliveira
Copy link

Any news on this?

@ae1080
Copy link

ae1080 commented Apr 12, 2017

any Updates?

@rblalock
Copy link

rblalock commented Jul 3, 2017

+100000 on this

@beeman
Copy link
Contributor

beeman commented Jul 3, 2017

This is another option based on @Tallyb's project https://github.com/BlueEastCode/loopback-graphql-relay

@smshuja
Copy link

smshuja commented Jul 17, 2017

Has there been any progress on this?

@abdonrd
Copy link

abdonrd commented Dec 25, 2017

Any progress? 🙂

@bajtos
Copy link
Member Author

bajtos commented Jan 5, 2018

See loopbackio/loopback-next#656 and https://github.com/strongloop/loopback4-extension-graphql

@bajtos bajtos closed this as completed Jan 5, 2018
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests