-
Notifications
You must be signed in to change notification settings - Fork 8
Migrate to use upstream GraphQL #41
Comments
Can I start working on it? |
The version which we are using has some additional go modules but the upstream version doesn't have it. And those modules are used widely in the project. So what should I do for them now? I can list the modules that are not in upstream if required. Chirino version was forked at this point and then he added modules over it https://github.com/graph-gophers/graphql-go/tree/25d6d94fa7a7f2b0ce10fd509e54e85f7a2f866b
|
Ok. I'm aware of this, but what you expect me to do with this info? What is your question? |
So my question is when I replace the imports everywhere from So how should I include those modules in our project? Like should I add them as modules in |
This is low level implementation question. I guess you need those from somewhere. |
Yeah, they are available in |
Not sure what you mean TBH. Let's create PR with explanation what was done. |
Okay sure @wtrocki, will create PR soon. After working on the issue, I will also have more clarity. |
Trust me - it will not be soon. There is more than week of work on migration IMHO. |
yeah realizing 🥲
okay, got it! |
@wtrocki Can you please assign this issue to me? Will start working on it right away |
Currently we are using Chirino fork of the GraphQL.
GraphQL implementation moved forward we should investigate how much work will be needed to migrate
The text was updated successfully, but these errors were encountered: