Why doesn't the fetchData function need to be an async/await function?

Question

I thought because there is a fetch() request inside the function, and because it is otherwise written as a synchronous event (regular function), that it had to be labeled as an async function with await after return and before fetch().

Here's the bit of code I'm referring to, specifically the first function:

function fetchData(url) {
  return fetch(url).then((res) => res.json());
}

fetchData("https://dog.ceo/api/breeds/image/random").then((data) =>
  generateImage(data.message)
);

fetchData("https://dog.ceo/api/breeds/list").then((data) =>
  generateList(data.message)
);

Thanks!

Answer 1 · 2020-06-03T00:37:46Z

June 3, 2020 12:37am

The code here is using "then" to make sure the operations occur at the right time. Using "then" is similar to using "await" except that "then" fires a separate callback function after the promise resolves, but "await" pauses the current function until the promise resolves.

Welcome to the Treehouse Community

Looking to learn something new?

Joseph Michelini

Joseph Michelini

Why doesn't the fetchData function need to be an async/await function?

1 Answer

Steven Parker

Steven Parker

Joseph Michelini

Joseph Michelini

Tashan Duncan

Tashan Duncan

Steven Parker

Steven Parker