Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for ability to chain operations #20

Closed
coco98 opened this issue Jan 5, 2023 · 0 comments
Closed

Add support for ability to chain operations #20

coco98 opened this issue Jan 5, 2023 · 0 comments

Comments

@coco98
Copy link
Contributor

coco98 commented 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?

@coco98 coco98 changed the title Add support for ability to Chain Add support for ability to chain operations Jan 5, 2023
@coco98 coco98 closed this as completed May 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant