Re:React, Relay and GraphQL: Under the Hood of the Times Web...
by djmashko2 on Saturday July 01, 2017 @01:13PM
(#14677915)
I think the parent is saying something different: They were happy with GraphQL for their API, but weren't happy with the requirements the Relay client library imposed.
My interpretation is that they are now using a GraphQL API but fetching from it with regular HTTP fetches and managing data with Redux on the frontend.
Re:React, Relay and GraphQL: Under the Hood of the Times Web...
by lioeters on Saturday July 01, 2017 @08:51PM
(#14680096)
Aha, thanks for the clarification. Upon reading the comment again, I see that it's Relay that didn't suit his use case, not GraphQL.
Re:React, Relay and GraphQL: Under the Hood of the Times Web...
by sAbakumoff on Saturday July 01, 2017 @01:27PM
(#14677989)
Yes exactly, thanks for your help.
Re:React, Relay and GraphQL: Under the Hood of the Times Web...
by sAbakumoff on Saturday July 01, 2017 @06:18PM
(#14679363)
What's wrong with inflammatory adjectives?
Re:React, Relay and GraphQL: Under the Hood of the Times Web...
by lioeters on Saturday July 01, 2017 @08:56PM
(#14680118)
Well, I just imagined that the devs of the library may be come across your comment and be offended/saddened to hear it being called "ridiculous" and "stupid". But then again, it sounds like you have good reasons to be frustrated with it, so why not. I recently saw someone write, "Webpack is ridiculous" - I suppose there's nothing wrong with inflammatory adjectives if it's backed up by evidence/experience.
As far as the criticism, would you be kind enough to explain what you mean by "relay concepts", and how GraphQL failed to satisfy those needs?