Is typescript-apollo-angular still actively maintained?

[ststroppel]

Hey everyone,
First off, I want to say that we love this project and have been using it across our tools for a while now. It's been a great help!
I'm writing to ask about the typescript-apollo-angular package specifically. I've noticed that it hasn't received many updates recently, aside from overall version bumps. There are also a few open pull requests that don't seem to have gotten much attention, and I was wondering if there are any plans to review or merge them.

We're keen to know if this package is still being actively maintained.
Thanks for all your work on this great tool

[eddeee888]

Hello! typescript-apollo-angular is a community plugin, so it's open for contributions.

Could you help me find the outstanding PRs please? I could help approve and move them, but ultimately the users of the plugin are in the best place to make improvements!

[Urigo]

@PowerKiKi your comment I think shows why we've placed this specific project under the community repo, as if as the main maintainer of apollo-angular you are not using or recommending it, then it is probably not recommended.
So if anyone wants to use it, they should step up and maintain that themselves.

@ststroppel can you share why do you think this project is important to you, compared to the approach recommended by apollo-angular?

[PowerKiKi]

@Urigo, it is true that I don't use @graphql-codegen/typescript-apollo-angular for my personal use, but instead @graphql-codegen/typescript-operations. But that has nothing to do with the value/quality of typescript-apollo-angular. If I don't use it, it is only because all my projects were created long before I discovered typescript-apollo-angular. And investigating it, and possibly migrating my projects to it, is far down in my priority list.

So, really, I just don't have any opinion about it. I can neither recommend for, nor against, it.

[ststroppel]

@Urigo, while the apollo-angular documentation shows how to define types manually, that is the exact step we want to avoid. In our opinion, typescript-apollo-angular provides significant value because it also generates the client code, ensuring that the GraphQL queries in our client application match the server's schema.

That brings us to the critical question that @PowerKiKi also mentioned: who can merge the existing and future PRs?

It's clear from the discussions and workarounds that the community is active and values this plugin. The bottleneck seems to be the final step of getting contributions reviewed and merged.

If there's no capacity from the core team to merge these PRs, then for the sake of transparency, we should probably update the documentation. We could declare the plugin as no longer maintained and point to some alternative solutions.

What are your thoughts on this?

[PowerKiKi]

declare the plugin as no longer maintained

I would prefer adding contributor(s) to this project, rather than split the community somewhere else. I think that the fact that the plugin lives in the same repo as the core has value, and should be preserved that way if reasonable.

... but I would rather not be the contributor on this 😅 (or as a last resort)

[Urigo]

Thank you both for the feedback!

@ststroppel are you using apollo-angular in production today?
Are you willing to step up as the community maintainer of the typescript-apollo-angular plugin?