# GraphQL is both a query language for APIs and a runtime for querying your data. GraphQL provides a complete, easy-to-understand description of the data in your API, allowing the client to get exactly the data it needs without any redundancy.
GraphQL has server-side implementations for different languages to help developers build GraphQL Server. (Recommended learning: Front-end video)
And gq-loader is a webpack plug-in. You can think of it as a client-side implementation for front-end projects. Its purpose is to help front-end development It makes it easier for students to call the GraphQL API. It makes it more convenient for front-end developers to use GraphQL, as easily as ordinary js modules. It allows front-end developers to import .gql and .graphql files in js files through import or require, and then Call directly.
And it also supports importing other .gql files, such as fragments, through #import syntax.
#import also provides two aliases, namely #require and #include. The usage and behavior of these two aliases are exactly the same as #import.
Installation
npm install gq-loader --save-dev
or
yarn add gq-loader
Basic use
Like other Loader is the same. First, we add the gq-loader configuration in webpack.config.js
{ test: /\.(graphql|gql)$/, exclude: /node_modules/, use: { loader: 'gq-loader' options: { url: 'Graphql Server URL' } } }
Then, we can import the .gql file in the js file and use it. Let’s do a simple As an example, assuming there is already a working Graphql Server, then we first create a getUser.gql that can query users
#import './fragment.gql' query MyQuery($name: String) { getUser(name: $name) ...userFields } }
As you can see, we reference another .gql file fragment through #import. gql, in this file we describe the field information of the user to be returned, so that we can "reuse" it in different places, we also create this file
fragment userFields on User { name age }
Okay, we can Directly import getUser.gql in the js file and use it to query users. It has never been easier. Let’s take a look.
import getUser from './getUser.gql'; import React from 'react'; import ReactDOM from 'react-dom'; async function query() { const user = await getUser({ name: 'bob' }); console.log('user', user); } function App() { return <button onClick={query}>click</button>; } ReactDOM.render(<App />, document.getElementById('root'));
When calling getUser, we can pass variables to GraphQL as function parameters. These variables These are our query parameters.
Custom request
The default gq-loader will help you complete the graphql request, but in some scenarios you may want to control all requests yourself, if so necessary , we can also "customize" the request through the request attribute. Take a look at the example. You need to slightly change the loader configuration first
{ test: /\.(graphql|gql)$/, exclude: /node_modules/, use: { loader: 'gq-loader' options: { url: 'Graphql Server URL', //指定自动请求模块路径 request: require.resolve('your_request_module_path'); } } }
Fill in the custom request module path in your_request_module_path, gq-loader will automatically load and use the corresponding Request module, the module only needs to change a "request function", see the following custom example
onst $ = require('jquery'); //url 是要请求的 GraphQL 服务地址 //data 是待发送的数据 //options 是自定义选项 module.exports = function(url, data, options){ //如果有需要还可以处理 options return $.post(url, data); };
Among them, options is the "second parameter of the function" after importing the .gql file, for example, it can be like this Pass the options parameter
import getUser from './getUser.gql'; async function query() { const options = {...}; const user = await getUser({ name: 'bob' }, options); console.log('user', user); }
Note that no matter what value is configured for the extensions of gq-loader, the extension cannot be omitted when importing in js. This option only applies to .gql file import and other .gql files
The above is the detailed content of How does the front end call GraphQL API?. For more information, please follow other related articles on the PHP Chinese website!

Using ID selectors is not inherently bad in CSS, but should be used with caution. 1) ID selector is suitable for unique elements or JavaScript hooks. 2) For general styles, class selectors should be used as they are more flexible and maintainable. By balancing the use of ID and class, a more robust and efficient CSS architecture can be implemented.

HTML5'sgoalsin2024focusonrefinementandoptimization,notnewfeatures.1)Enhanceperformanceandefficiencythroughoptimizedrendering.2)Improveaccessibilitywithrefinedattributesandelements.3)Addresssecurityconcerns,particularlyXSS,withwiderCSPadoption.4)Ensur

HTML5aimedtoimprovewebdevelopmentinfourkeyareas:1)Multimediasupport,2)Semanticstructure,3)Formcapabilities,and4)Offlineandstorageoptions.1)HTML5introducedandelements,simplifyingmediaembeddingandenhancinguserexperience.2)Newsemanticelementslikeandimpr

IDsshouldbeusedforJavaScripthooks,whileclassesarebetterforstyling.1)Useclassesforstylingtoallowforeasierreuseandavoidspecificityissues.2)UseIDsforJavaScripthookstouniquelyidentifyelements.3)Avoiddeepnestingtokeepselectorssimpleandimproveperformance.4

Classselectorsareversatileandreusable,whileidselectorsareuniqueandspecific.1)Useclassselectors(denotedby.)forstylingmultipleelementswithsharedcharacteristics.2)Useidselectors(denotedby#)forstylinguniqueelementsonapage.Classselectorsoffermoreflexibili

IDsareuniqueidentifiersforsingleelements,whileclassesstylemultipleelements.1)UseIDsforuniqueelementsandJavaScripthooks.2)Useclassesforreusable,flexiblestylingacrossmultipleelements.

Using a class-only selector can improve code reusability and maintainability, but requires managing class names and priorities. 1. Improve reusability and flexibility, 2. Combining multiple classes to create complex styles, 3. It may lead to lengthy class names and priorities, 4. The performance impact is small, 5. Follow best practices such as concise naming and usage conventions.

ID and class selectors are used in CSS for unique and multi-element style settings respectively. 1. The ID selector (#) is suitable for a single element, such as a specific navigation menu. 2.Class selector (.) is used for multiple elements, such as unified button style. IDs should be used with caution, avoid excessive specificity, and prioritize class for improved style reusability and flexibility.


Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

MinGW - Minimalist GNU for Windows
This project is in the process of being migrated to osdn.net/projects/mingw, you can continue to follow us there. MinGW: A native Windows port of the GNU Compiler Collection (GCC), freely distributable import libraries and header files for building native Windows applications; includes extensions to the MSVC runtime to support C99 functionality. All MinGW software can run on 64-bit Windows platforms.

Dreamweaver Mac version
Visual web development tools

MantisBT
Mantis is an easy-to-deploy web-based defect tracking tool designed to aid in product defect tracking. It requires PHP, MySQL and a web server. Check out our demo and hosting services.

WebStorm Mac version
Useful JavaScript development tools

Zend Studio 13.0.1
Powerful PHP integrated development environment
