Open tonyhb opened 7 years ago
I could see value in supporting both REST and GraphQL endpoints to allow for seamless client-side cross endpoint model resolution, although I have not run into this requirement since it is already so easy to include any dependent REST data into a GraphQL service's resolver. And in cases where REST and GraphQL data are used for completely separate components, it is easy to use Tectonic and Apollo in parallel.
Good to know, thanks for the heads up!
On Wed, Jun 21, 2017, 9:25 AM Alex Freska notifications@github.com wrote:
I could see value in supporting both REST and GraphQL endpoints to allow for seamless client-side cross endpoint model resolution, although I have not run into this requirement since it is already so easy to include any dependent REST data into a GraphQL service's resolver. And in cases where REST and GraphQL data are used for completely separate components, it is easy to use Tectonic and Apollo in parallel.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/tonyhb/tectonic/issues/91#issuecomment-310132681, or mute the thread https://github.com/notifications/unsubscribe-auth/AASsAW-eRX8FrQp6EQ9PiZGrmEzKa5gTks5sGUPzgaJpZM4N4xWB .
can we integrate graphql into this? plz investigate. any comments/ideas welcome