You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A function that does not contain any await expressions should not be async (except for some edge cases in TypeScript which are discussed below). Asynchronous functions in JavaScript behave differently than other functions in two important ways:
The return value is always a Promise.
You can use the await operator inside them.
Functions are made async so that we can use the await operator inside them. Consider this example:
async function fetchData(processDataItem) {
const response = await fetch(DATA_URL);
const data = await response.json();
return data.map(processDataItem);
}
Asynchronous functions that don't use await might be an unintentional result of refactoring.
Note: This issue ignores async generator functions. Generators yield rather than return a value and async generators might yield all the values of another async generator without ever actually needing to use await.
In TypeScript, one might feel the need to make a function async to comply with type signatures defined by an interface. Ideally, the code should be refactored to get rid of such restrictions, but sometimes that isn't feasible (For example, when we are implementing an interface defined in a 3rd party library like Next.js).
This situation can easily be circumvented by returning the value with a call to Promise.resolve:
// Recommended:
const o: HasAsyncFunc = {
// We only use Promise.resolve to adhere to the type
// of the surrounding object.
getNum() { return Promise.resolve(1) }
}
It is also advised to add a comment near the redundant promise to make the intent clear.
BAD PRACTICE
async function fetchData(): string {
// readFileSync is a synchronous function that blocks
// the main thread, and thus does not need to be awaited
return fs.readFileSync("data.txt", "utf-8");
}
performAction(async () => { console.log("no awaits in here") });
RECOMMENDED
async function fetchDataAsync(): Promise {
return await fs.readFile("data.txt", "utf-8")
}
DESCRIPTION
A function that does not contain any await expressions should not be async (except for some edge cases in TypeScript which are discussed below). Asynchronous functions in JavaScript behave differently than other functions in two important ways:
The return value is always a Promise.
You can use the await operator inside them.
Functions are made async so that we can use the await operator inside them. Consider this example:
async function fetchData(processDataItem) {
const response = await fetch(DATA_URL);
const data = await response.json();
}
Asynchronous functions that don't use await might be an unintentional result of refactoring.
Note: This issue ignores async generator functions. Generators yield rather than return a value and async generators might yield all the values of another async generator without ever actually needing to use await.
In TypeScript, one might feel the need to make a function async to comply with type signatures defined by an interface. Ideally, the code should be refactored to get rid of such restrictions, but sometimes that isn't feasible (For example, when we are implementing an interface defined in a 3rd party library like Next.js).
This situation can easily be circumvented by returning the value with a call to Promise.resolve:
interface HasAsyncFunc {
getNum: () => Promise
}
// Not recommended:
const o: HasAsyncFunc = {
async getNum() { return 1 }
}
// Recommended:
const o: HasAsyncFunc = {
// We only use
Promise.resolve
to adhere to the type// of the surrounding object.
getNum() { return Promise.resolve(1) }
}
It is also advised to add a comment near the redundant promise to make the intent clear.
BAD PRACTICE
async function fetchData(): string {
//
readFileSync
is a synchronous function that blocks// the main thread, and thus does not need to be
await
edreturn fs.readFileSync("data.txt", "utf-8");
}
performAction(async () => { console.log("no awaits in here") });
RECOMMENDED
async function fetchDataAsync(): Promise {
return await fs.readFile("data.txt", "utf-8")
}
performAction(async () => { await writeToFile(data) });
// Allow empty functions.
async function no_op() {}
Look here to fix it:
Found async function without any await expressions
src/api.ts
*/
export const retryCalls = async (
provider: ProviderLike,
addresses: string | string[],
contracts: string | string[],
results: Result[],
encodeData: (address: string) => string
): Promise<Result[]> => {
return Promise.all(
results.map(async (result, index) => {
if (result[0]) {
return result;
}
const address = typeof addresses === 'string' ? addresses : addresses[index];
const contractAddress = typeof contracts === 'string' ? contracts : contracts[index];
const data = encodeData(address);
try {
const newResult = await call(provider, contractAddress, data);
return [true, newResult] as [boolean, Uint8Array];
} catch {
// noop
}
return result;
})
);
};
Found async function without any await expressions
src/providers/eip-1193.ts
},
send: async (provider: EIP1193ProviderLike, method: string, params: unknown[]): Promise => {
const payload = getPayload(method, params);
return provider.request(payload);
}
};
export default provider;
Found async function without any await expressions
src/providers/provider.test.ts
jest.mock('./eip-1193', () => ({
isProvider: jest.fn(),
send: jest.fn().mockImplementation(async () => '0x00')
}));
jest.mock('./ethers', () => ({
Found async function without any await expressions
src/providers/provider.test.ts
jest.mock('./ethers', () => ({
isProvider: jest.fn(),
send: jest.fn().mockImplementation(async () => '0x00')
}));
jest.mock('./http', () => ({
Found async function without any await expressions
src/providers/provider.test.ts
jest.mock('./http', () => ({
isProvider: jest.fn(),
send: jest.fn().mockImplementation(async () => '0x00')
}));
jest.mock('./web3', () => ({
1
2
The text was updated successfully, but these errors were encountered: