I ran into problems with the native GraphQL implementation in 3.3 and continued using CraftQL on my latest few projects. I'm not so happy about that decision because CraftQL clearly isn't getting updates from the developer any longer and I've found more than a few bugs or problem areas and I imagine will only get more broken as Craft continues to be updated. I've also hit a few snags with performance in CraftQL and ended up branching it to add my own caching logic.
I'm happy to say that the native GraphQL implementation has improved quite a bit in Craft 3.4. You can now query entries by field value, and combine multiple relatedTo queries more easily.
Combining multiple relatedTo queries was particularly challenging in CraftQL so this is a very welcome improvement. Not to mention built-in caching plus the support and ongoing development from the P&T team means it would be very hard to justify using CraftQL on future projects.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I ran into problems with the native GraphQL implementation in 3.3 and continued using CraftQL on my latest few projects. I'm not so happy about that decision because CraftQL clearly isn't getting updates from the developer any longer and I've found more than a few bugs or problem areas and I imagine will only get more broken as Craft continues to be updated. I've also hit a few snags with performance in CraftQL and ended up branching it to add my own caching logic.
I'm happy to say that the native GraphQL implementation has improved quite a bit in Craft 3.4. You can now query entries by field value, and combine multiple relatedTo queries more easily.
github.com/craftcms/cms/issues/5200
github.com/craftcms/cms/issues/5208
Combining multiple relatedTo queries was particularly challenging in CraftQL so this is a very welcome improvement. Not to mention built-in caching plus the support and ongoing development from the P&T team means it would be very hard to justify using CraftQL on future projects.