vnovick / ama

Ask me anything!
https://github.com/vnovick/ama/issues?q=is%3Aissue+is%3Aclosed
2 stars 1 forks source link

Your preferred filtering strategy for GraphQL #2

Open wtrocki opened 4 years ago

wtrocki commented 4 years ago

Projects like hasura or prisma generate a lots of input fields to build query filtering capabilities. Example: https://docs.hasura.io/1.0/graphql/manual/queries/query-filters.html

I often see a lots of criticism of this approach when compared to queries incorporated into schema. What will be your opinion on that manner?

Do you prefer "anemic filtering" using generics where single find can be used for multiple purposes or dedicated find operations that incorporates filtering in resolver layer?

Do you see recent changes in GraphQL spec helping developers to build better filtering - InputUnions etc.?