A new path for graphql-config - help us decide on the roadmap!

[Urigo]

Hi everyone!

I'm @Urigo the founder of The Guild.

As recently been announced on the Prisma blog, we are taking over the maintenance of this library going forward.
I've expressed it in the blog post in more details but I would like to start by thanking Prisma for conceiving, creating and maintaining this library so far and also for doing the selfless act of providing it with fresh life by handing over the maintenance to us.

We already have a certain plan in mind going forward, some of it we've specified in the blog post, but we want you, the users and community of the library to be part of influencing the roadmap going forward.

One thing to note about The Guild - We place all the open source packages we maintain under individual person's Github profile instead of under a GitHub org or a company.
That is part of our philosophy - it puts more accountability on the maintainer and it also lowers the barrier of creating successful competing forks.
So we will transfer that repository from under Prisma as part of the transition.

I'm looking forward to start the discussion here below.
Please share how and why you use the library today, what are your biggest pain points today and ideas and features you would like to see in the future.

I will add points into the description here as we go.

Let's make this happen!

[kdawgwilk]

My biggest pain point is around refresh tokens used by OAuth applications that have fairly short lived timeouts. The company I work for is a FinTech company which requires conformance to certain security standards such as PCI. This requires us to re-authenticate a user every 10 min which creates a new refresh token. By not being able to dynamically change a header found in .graphqlconfig makes it a major pain to use for me since I have to manually update the token every 10 min.

[tvvignesh]

@schickling @yoshiakis I am not sure who is maintaining Playground now, but considering that the syntax of graphql-config has changed, are there any plans to use the newer version?

Also, it would be great to provide some sort of compatibility with Apollo Config (https://www.apollographql.com/docs/devtools/apollo-config/) - otherwise, we are going to maintain 2 config files for GraphQL.

Thanks.

[Urigo]

We are about to release a new major version for graphql-config.
Developers and library maintainers, please make sure you add all your needs and wishes soon so we would be able to take them into account on the next version.
Also fell free to contact us if you need help with the migration.

[acao]

@schickling @yoshiakis I am not sure who is maintaining Playground now, but considering that the syntax of graphql-config has changed, are there any plans to use the newer version?

Also, it would be great to provide some sort of compatibility with Apollo Config (https://www.apollographql.com/docs/devtools/apollo-config/) - otherwise, we are going to maintain 2 config files for GraphQL.

Thanks.

we took over basic maintenance of playground, however have had issues getting another electron release out, because the build was broken when we adopted the project. there is a PR open however! if you could help review that. also vscode-graphql which also uses the official LSP is using graphql config 3.3.x!

[tvvignesh]

@acao Thanks for the clarity (I actually came across that later and had also blogged about VSCode GraphQL, GraphiQL, GraphQL.js and playground as well as part of a blog series here: https://the-guild.dev/blog/graphql-deep-dive-1).

I actually switched to using GraphiQL from Playground. So, I should be good to go from my end as of now. I am not sure if I am knowledgeable to review a PR from GraphiQL as of now, but do let me know where I can help. Thanks.