From 39d1fc472097a94d6a9b78863baafb3285f76f69 Mon Sep 17 00:00:00 2001 From: Dave Lockhart Date: Thu, 3 Aug 2023 15:10:45 -0400 Subject: [PATCH] Update README.md Co-authored-by: Margaree Peacocke --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index d9a26425..370f194f 100644 --- a/README.md +++ b/README.md @@ -230,7 +230,7 @@ it('should wait', async() => { #### Waiting For Asynchronous Components -`fixture()` will automatically wait for all nested Lit components to fulfill their `updateComplete` Promise. To tweak when a component's `updateComplete` fulfills, implement the [getUpdateComplete() lifecycle callback](https://lit.dev/docs/components/lifecycle/#getUpdateComplete). +`fixture()` will automatically wait for all nested Lit components to fulfill their `updateComplete` Promise. To tweak when a component's `updateComplete` fulfills, implement the [`getUpdateComplete()` lifecycle callback](https://lit.dev/docs/components/lifecycle/#getUpdateComplete). In other scenarios, a component may have an initial loading state (e.g. loading spinner or skeleton) where `updateComplete` has already resolved in addition to another fully loaded state. To signal that `fixture()` should wait for this final state, implement `getLoadingComplete()`. It works the same way as `getUpdateComplete()` by fulfilling its Promise when the component has fully loaded.