You’re right that there will need to be long-term support of API versions (or at least the current one and maybe the previous one).
My instinct is to give the users the full objects and let them select the fields they want on their side. It’s less work on our side. Also I’m not sure about customer comfort with GraphQL.
Where GraphQL really shines is in the synthetic fields - the ones that are just too expensive to compute for all requests, but kind of make sense to have en the entity.
Most interesting applications have some type of properties of entities that transcent a static object.
You’re right that there will need to be long-term support of API versions (or at least the current one and maybe the previous one).
My instinct is to give the users the full objects and let them select the fields they want on their side. It’s less work on our side. Also I’m not sure about customer comfort with GraphQL.