Skip to main content
Version: v2

Skills

The following are the better usage skills used by alova developers when using alova. They are collected from multiple parties and organized here. I hope that everyone can use alova more smoothly.

Send request useRequest OR method

The useRequest provided by alova will only send a request and get the response data under normal circumstances, so why not use the method instance to send the request directly, because useRequest can help us automatically manage loading and data , error and other responsive data that can be used directly, so if you need to use these states, use useRequest without maintaining the data yourself. But on the contrary, you don't need to only apply useRequest in the whole project. For example, when you only care about getting information and don't need to use loading, error, etc., when getting data outside the component, you can use method instance to send the request.

Update state and cache at the same time

When you finish editing a piece of data in a list, you don't want to re-request to update the list data again, but manually update the list data. Many developers may directly modify the list data.

<template>
<List :data="listData"></List>
<Editor @submit="handleItemSubmit"></Editor>
</template>
<script setup>
//...

const { data: listData } = useRequest(getList, {
initialData: []
});

// directly updated listData
const handleItemSubmit = item => {
const index = listData.findIndex(({ id }) => id === item.id);
listData.splice(index, 1, item);
};
</script>

❌ This way of writing is not recommended

Although this can trigger the interface to refresh, it may cause another problem, that is, when the list data is cached, because the cached data has not been updated, the hit cache is still the original data when entering the list page again.

So you can call updateState to update the stateful data and update the cache immediately.

<template>
<List :data="listData"></List>
<Editor @submit="handleItemSubmit"></Editor>
</template>
<script setup>
//...

const { data: listData } = useRequest(getList, {
initialData: []
});

// Update listData through updateState, the cache will be updated at the same time
const handleItemSubmit = item => {
updateState(getList(), oldListData => {
const index = oldListData.findIndex(({ id }) => id === item.id);
oldListData.splice(index, 1, item);
return oldListData;
});
};
</script>

Quickly get sendArgs in onSuccess

In actual projects, data is often passed through the send function. If you need to use these data in callback functions such as onSuccess, since they exist in the event.sendArgs array, you can use the double destructuring method to directly obtain them to the data.

onSuccess(({ sendArgs: [content] }) => {
console.log(content);
});

Use prefixes to manage similar method instances

In many scenarios, we need to invalidate multiple caches at the same time. For example, the data of a page comes from multiple interfaces. When editing the data of this page, it is necessary to invalidate the cached data of these interfaces at the same time. You can method instances with the same prefix to classify them, and use this regex to invalidate caches with the same prefix.

const getData1 = id => alovaInstance.Get('/data1', {
name: `data-${id}-1`,
params: {
id
}
});
const getData2 = id => alovaInstance.Get('/data2', {
name: `data-${id}-2`,
params: {
id
}
});
const getData3 = id => alovaInstance.Get('/data3', {
name: `data-${id}-3`,
params: {
id
}
});

const handleInvalidateCache = id => {
// Simultaneously invalidate the 3 cached data of the specified id
invalidateCache(new RegExp(`^data-${id}`);
}

Mock data practice

If your project needs to use mock data to simulate some or all interfaces in the development environment, and switch back to real network requests in production, you can control it through environment variables.

const globalFetch = GlobalFetch();
const mockAdapter = createAlovaMockAdapter([mockGroup1 /** ... */], {
httpAdapter: globalFetch,
delay: 1000
});

export const alovaInst = createAlova({
baseURL: 'http://xxx',

// Control the production environment through environment variables, and will not package mock related codes
requestAdapter: process.env.NODE_ENV === 'development' ? mockAdapter : globalFetch
//...
});

And it is recommended that different developers in the team can create different mock interface data according to the version number of each iteration, so as to manage these mock data in the team. For details, please refer to the chapter of mock Data .

Use useRequest to make parallel requests

For simple parallel requests, you only need to call multiple useRequest at the same time.

const { data: todoList } = useRequest(todoListGetter);
const { data: todoCounter } = useRequest(todoCountGetter);

But such a request only applies to simple parallel requests. If you need to perform certain operations after all parallel requests are completed, there are two ways to achieve it:

method 1

Manually create a promise object and use Promise.all to complete the effect.

const {
data: todoList,
onSuccess: onListSuccess,
onError: onListError
} = useRequest(todoListGetter);
const {
data: todoCounter,
onSuccess: onCountSuccess,
onError: onCountError
} = useRequest(todoCountGetter);

// Manually create promise object
const listPromise = new Promise((resolve, reject) => {
onListSuccess(resolve);
onListError(reject);
});
const countPromise = new Promise((resolve, reject) => {
onCountSuccess(resolve);
onCountError(reject);
});
const [listEvent, countEvent] = await Promise.all([listPromise, countPromise]);
// Parallel request is completed, continue processing business...

Method 2

Using the send function returned by the useRequest function, calling send will return a usable promise object.

// Let them not automatically send requests first
const { send: sendList } = useRequest(todoListGetter, { immediate: false });
const { send: sendCount } = useRequest(todoCountGetter, { immediate: false });

//Use the promise object returned by the send function
const parallelRequest = async () => {
const [listResponse, countResponse] = await Promise.all([sendList(), sendCount()]);
// Parallel request is completed, continue processing business...
};

Use useRequest serial request

Serial requests also have two modes.

method 1

Let the first request be sent automatically, and the second request be triggered in the onSuccess callback of the first request to complete the serial request. The serial request can be completed by the following writing method:

//
const { data: todoList, onSuccess } = useRequest(todoListGetter);
const { data: todoDetail, send: sendTodoDetail } = useRequest(
todoId => todoDetailGetter(todoId),
{ immediate: false }
);

// Get the list first, then get the details of the first todo
onSuccess(event => {
sendTodoDetail(event.todoList[0].id);
});

Method 2

Using the send function returned by the useRequest function, calling send will return a usable promise object.

// Let them not automatically send requests first
const { send: sendList } = useRequest(todoListGetter, { immediate: false });
const { send: sendTodoDetail } = useRequest(todoId => todoDetailGetter(todoId), {
immediate: false
});

//Use the promise object returned by the send function
const serialRequest = async () => {
const todoList = await sendList();
const todoDetail = await sendTodoDetail(todoList[0].id);
// The serial request is completed, continue processing business...
};

For serial requests, it is recommended to use useSerialRequest and useSerialWatcher directly.