For now, it only contains a single query called hello , which will then returns a string. It just resolves the value of hello query that we define in the typeDefs. Let's say we want to create a server that provides a list of books and those authors. We can store it inside the data. Here, we have an array of authors that has a name and email.
Each of them also has their own unique id which allows us to relate them into another data type, which in this case is the books. In the book data type, we have the title as well as the id. We also have the author, which refers to the author of that book. Now, I hope you get the idea right. An author can have multiple books, but a book can only have a single author. Then, we define the resolver of the books query, which is pretty straightforward. And the reason why get null in the author field is because we don't tell the server how to get those authors.
So, let's make some adjustments in our resolvers. Now, we can get the author by using the parent value that passed to the resolver function and find the author by that id. Now, here is the thing. And here is how it looks like. Then, run the server and execute the previous GraphQL query to fetch all books and those authors.
Even though we only have two authors, we're fetching them four times. And this is not an efficient approach because we're trying to fetch the same author over and over again. Imagine if these data are stored inside a database. How long does it takes to run those queries, even though we can get all of them at the same time with a single query.
It allows us to bulk the process of fetching those relational data, so that we can query them at the same time. To make the same transformation work in FuseBox, use fuse-box-graphql-plugin. React native can't use the Webpack loaders. To make the same transformation work in React native, use babel-plugin-import-graphql. To make the same transformation work in create-react-app without ejecting, use graphql.
You can use and include fragments in. See how we import the UserInfo fragment from another. These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work.
These cookies do not store any personally identifiable information. These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous.
If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance. These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages.
If you do not allow these cookies then some or all of these services may not function properly. These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising.
This website uses cookies to ensure you receive the best possible experience. Learn More. Loading queries with Webpack.
0コメント