Skip to content
This repository has been archived by the owner on Mar 3, 2020. It is now read-only.

Porting an existing graphql-yoga application #36

Open
rush-levint opened this issue Jul 5, 2018 · 1 comment
Open

Porting an existing graphql-yoga application #36

rush-levint opened this issue Jul 5, 2018 · 1 comment

Comments

@rush-levint
Copy link

Hi, how do you advise porting an existing graphql application into Hadron? Hadron sports a structure that I find highly desirable and appropriate for my project.

@marekbrainhub
Copy link
Member

Hello,

Hadron is still a maturing ecosystem and while we've been looking into a dedicated package for GraphQL, there aren't any particularly good ways to implement it right now. However, we've discussed this briefly and we'll look into implementing a more elegant, if temporary, solution to this.

There is a workaround, of course, however since you've said you want to port an entire application to Hadron, I don't think a workaround is a suitable solution.

We'll keep this open for now.

@marekbrainhub marekbrainhub changed the title Porting ang existing graphql-yoga application Porting an existing graphql-yoga application Jul 5, 2018
szymonbrainhub added a commit that referenced this issue Jul 12, 2018
 Adding an option to add own handlers for routing (#36)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants