I didn't say it was a unique thing to graphQL. I was explaining why graphQL isn't a 1:1 replacement for REST because of that. I feel like you are hearing an a

I didn't say it was a unique thing to graphQL. I was explaining why graphQL isn't a 1:1 replacement for REST because of that. I feel like you are hearing an argument that I am not making. Use whatever tool is best for the job / infrastructure / business needs. If that's Django cool. GraphQL has its place too.