2020-05-13
3398
#graphql
Leonardo Losoviz
18500
May 13, 2020 ⋅ 12 min read

GraphQL directives are underrated

Leonardo Losoviz Freelance developer and writer, with an ongoing quest to integrate innovative paradigms into existing PHP frameworks, and unify all of them into a single mental model.

Recent posts:

react toastify

React-Toastify (2025 update): Setup, styling & real-world use cases

Learn how to use React-Toastify in 2025, from setup to styling and advanced use cases like API notifications, async toasts, and React-Toastify 11 updates.

Chimezie Innocent
Apr 18, 2025 ⋅ 18 min read
5 Best Open Source Tools For Cross-Browser CSS Testing

5 best open source tools for cross-browser CSS testing

Discover open source tools for cross-browser CSS testing like Playwright and BrowserStack to catch rendering errors, inconsistent styling, and more.

Peter Aideloje
Apr 18, 2025 ⋅ 11 min read
react suspense data fetching

How to handle data fetching with React Suspense

With the introduction of React Suspense, handling asynchronous operations like data fetching has become more efficient and declarative.

Ovie Okeh
Apr 18, 2025 ⋅ 10 min read
Use TypeScript Instead Of Python For ETL Pipelines

Use TypeScript instead of Python for ETL pipelines

Build a TypeScript ETL pipeline that extracts, transforms, and loads data using Prisma, node-cron, and modern async/await practices.

Muhammed Ali
Apr 17, 2025 ⋅ 6 min read
View all posts

3 Replies to "GraphQL directives are underrated"

  1. Good post thanks.

    Small correction that otherwise might confuse some:
    * “All others (analytics/logging/metrics, authorization, caching, configuring default values, validation) are of the *SCHEMA* type.”

  2. Great work !!. I have tried Custom Query-type directives which i have created but they are not working. Only skip and include are working on client query. Is there any reason for it ?

Leave a Reply