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
Based on a conversation with Pierre on the Legend team at GS:
Aggregations on a GraphQL API are much harder for data consumers to pick up and use, and people prefer a tabular data structure that they can project, filter and aggregate. The reason they prefer the tabular structure is because they aren't constrained by the type system and can easily chain a sequence of operations. This is the KEY ask for teams working in financial services.
What would the equivalent in the GraphQL world be?
Eg: Do we need to introduce meta type to represent a tabular structure that can be introspected on the fly - to permit tools like graphiql, graphql-codegen to validate queries entirely on the client side?
The text was updated successfully, but these errors were encountered:
coco98
changed the title
Add support for ability to Chain
Add support for ability to chain operations
Jan 5, 2023
Based on a conversation with Pierre on the Legend team at GS:
Aggregations on a GraphQL API are much harder for data consumers to pick up and use, and people prefer a tabular data structure that they can project, filter and aggregate. The reason they prefer the tabular structure is because they aren't constrained by the type system and can easily chain a sequence of operations. This is the KEY ask for teams working in financial services.
What would the equivalent in the GraphQL world be?
Eg: Do we need to introduce meta type to represent a tabular structure that can be introspected on the fly - to permit tools like graphiql, graphql-codegen to validate queries entirely on the client side?
The text was updated successfully, but these errors were encountered: