chore: type [ci skip]

This commit is contained in:
那里好脏不可以
2022-05-10 10:51:51 +08:00
committed by GitHub
parent 181872f744
commit 6042ab0f2f
22 changed files with 32 additions and 32 deletions

View File

@@ -1032,7 +1032,7 @@ describe('Suspense', () => {
await nextTick()
expect(deps.length).toBe(2)
// switch before two resovles
// switch before two resolves
view.value = Three
await nextTick()
expect(deps.length).toBe(3)
@@ -1098,7 +1098,7 @@ describe('Suspense', () => {
await nextTick()
expect(deps.length).toBe(2)
// switch back before two resovles
// switch back before two resolves
view.value = One
await nextTick()
expect(deps.length).toBe(2)

View File

@@ -183,7 +183,7 @@ describe('error handling', () => {
})
// unlike other lifecycle hooks, created/beforeCreate are called as part of
// the options API initiualization process instead of by the renderer.
// the options API initialization process instead of by the renderer.
test('in created/beforeCreate hook', () => {
const err = new Error('foo')
const fn = jest.fn()

View File

@@ -1,5 +1,5 @@
// since v-memo really is a compiler + runtime combo feature, we are performing
// more of an itegration test here.
// more of an integration test here.
import { ComponentOptions, createApp, nextTick } from 'vue'
describe('v-memo', () => {

View File

@@ -879,7 +879,7 @@ describe('renderer: optimized mode', () => {
// #3881
// root cause: fragment inside a compiled slot passed to component which
// programmatically invokes the slot. The entire slot should de-opt but
// the fragment was incorretly put in optimized mode which causes it to skip
// the fragment was incorrectly put in optimized mode which causes it to skip
// updates for its inner components.
test('fragments inside programmatically invoked compiled slot should de-opt properly', async () => {
const Parent: FunctionalComponent = (_, { slots }) => slots.default!()