New Home -> github.com/graphql-go/graphql about graphql HOT 10 CLOSED

👍 * 💯

from graphql.

Good stuff! I wonder if @sogko would be interested in moving the graphql-relay-go project to graphql-go as well.

from graphql.

This is great! I've been really excited for this! 👍🏻

@F21 Yeap, thats part of the plan, to consolidate core graphql-go components within the ecosystem into the organization's repo.

I have moved the following repos into graphql-go:

• graphql-relay-go
• graphql-go-handler
• golang-graphql-playground

There are other little example projects that I've written. They are not core components but could possibly go into graphql-go, let me know if you guys think it make sense to move them. I would love to encourage the community to pick it up and maintain it together if the examples prove helpful to them.

• https://github.com/sogko/golang-relay-starter-kit
• https://github.com/sogko/todomvc-relay-go

For example, golang-relay-starter-kit's JS equivalent relay-starter-kit is in github.com/relayjs, not github.com/graphql

Let me know what you guys think.

Also, anyone is welcome to beat me to the punch and send PRs for any of the other projects to fix broken import paths, etc 👍🏻

Cheers guys! Let's do this!

from graphql.

really cool 👍

from graphql.

Oops, one more thing that I forgot to mention.

Regarding the newly-transferred repos, I would like to hear feedback for their repo names and package names.

Here's my initial suggestions:

Welcome any feedback 👍🏻

from graphql.

@sogko That sounds good to me!

from graphql.

@sogko all good to me

from graphql.

@sogko LGTM 👍

from graphql.

Updates:
I've renamed the repos and packages as mentioned above, and updated them with the new import paths.

from graphql.

Updates:
I've renamed the repos and packages as mentioned above, and updated them with the new import paths.

Great! 🌟 thanks for updates, I def agree on following Go pkg short naming convention
across all graphql-go libs.

from graphql.