You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of the updates in Apollo Kotlin v3, a lot of the features requested on our backlog are now supported there.
Do we want to keep maintaining a separate client module that does most of the same features? Somethings missing is the direct support for a Maven plugin version. There are some community versions but maybe that we could create a new one that supports v3 in a separate repo.
This is just an open discussion, so feel free to shoot me down, but I am just considering what would be the value of now spending time to maintain a different client package, instead of consolidating on a single one for the community.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
As part of the updates in Apollo Kotlin v3, a lot of the features requested on our backlog are now supported there.
Do we want to keep maintaining a separate client module that does most of the same features? Somethings missing is the direct support for a Maven plugin version. There are some community versions but maybe that we could create a new one that supports v3 in a separate repo.
This is just an open discussion, so feel free to shoot me down, but I am just considering what would be the value of now spending time to maintain a different client package, instead of consolidating on a single one for the community.
Beta Was this translation helpful? Give feedback.
All reactions