hbar1st

id	69e16a610b33e847d85be16e
title	Step 27
challengeType	0
dashedName	step-27

--description--

At this point, the behaviour of the app should not have changed. The code still fetches a file from the CDN and then processes the retrieved data into JSON. Once that's done, it saves that data into the authorDataArr variable and then calls displayAuthors.

hbar1st

@freecodecamp/curriculum:test-content:        ❯ Block: workshop-fcc-authors-page (5)
@freecodecamp/curriculum:test-content:          ❯ Title: Step 25 (5)
@freecodecamp/curriculum:test-content:            ❯ ID: 69df434b56d2e0faf1a7424c (5)
@freecodecamp/curriculum:test-content:              ✓ Matches an ID in workshop-fcc-authors-page.json 0ms
@freecodecamp/curriculum:test-content:              ✓ Common checks 1ms
@freecodecamp/curriculum:test-content:              ✓ Has challenge files 0ms
@freecodecamp/curriculum:test-content:              ✓ Test suite must fail on the initial contents 36ms
@freecodecamp/curriculum:test-content:              ❯ Check tests against solutions (1)
@freecodecamp/curriculum:test-content:                × Solution 1 must pass the tests 8ms
@freecodecamp/curriculum:test-content:

hbar1st

id	69df434b56d2e0faf1a7424c
title	Step 25
challengeType	0
dashedName	step-25

--description--

Now that your fCC Authors Page is fully functional, let's refactor it to improve its readability by using async and await instead of the promise chaining method then.

hbar1st

//step-1

In this workshop, you will practice working with the async and await methods by refactoring the fCC Authors Page app you built in a prior workshop.

Recall that in order to use the await operator to wait for a function that returns a Promise, you need to wrap the function call in an async function.

An example of an async function declaration is:

const functionName = async () => {}

hbar1st

# Heavily borrowed from https://gist.github.com/neftaly/6390a8b3bfc278113d1a42303532d9b2

name: Build and Deploy

# Controls when the action will run. 
on:
  # Triggers the workflow on push or pull request events but only for the main branch
  push:
    branches: [ main ]

hbar1st

# Heavily borrowed from https://gist.github.com/neftaly/6390a8b3bfc278113d1a42303532d9b2

name: Build and Deploy

# Controls when the action will run. 
on:
  # Triggers the workflow on push or pull request events but only for the main branch
  push:
    branches: [ main ]