You then build specific queries that will scrupulously respect these descriptions and fetch the exact data that has been requested. GraphQL was intended as a way to avoid overfetching in other approaches such as REST APIs: you describe exactly what resources you will expose and how you want to expose them. As an introductory article, but taking advantage of some initial notes. So I have taken as an excuse the intention of publishing five basic ideas about GraphQL in Drupal. In fact I wouldn’t convince you to use GraphQL in your project, but there are situations where someone may be conditioned by circumstances to work with GraphQL. I’m not a GraphQL advocate, I think there are already many people and many platforms that do it quite well, so I’m not interested in holy wars. I have been working on openly decoupled Drupal projects for some time now, and I would like to share some experiences. Picture from Unsplash, user Masjid Pogung Dalangan, of sectionsĤ- Maintain your code clean and do refactoring ![]() As an introduction, I would like to share some initial thoughts based only on my observations. This article is oriented to this last opinion, the possibility of using GraphQL in Drupal, and is edited and published as the first post of a series about GraphQL. You can use REST, JSON:API or GraphQL as well. In this context, you will use some kind of specification or API connection to make backend and frontend work well and understand each other. splitting into several parts of different technology, leaving Drupal only for the backend side of the project. ![]() ![]() Usually, this way of working necessarily involves “breaking the monolith” i.e. You’ve probably heard of “decoupled Drupal” or “headless”, a way of working with Drupal that consists of separating the frontend from the backend, implementing communication between both parts as separate projects, distinct repositories, etc.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |