Red Huang

 const state = reactive({
  count: 0,
  double: computed(() => state.count * 2)
}) 

 it('should return updated value', () => {
    const value = reactive<{ foo?: number }>({})
    const cValue = computed(() => value.foo)
    expect(cValue.value).toBe(undefined)
    value.foo = 1
    expect(cValue.value).toBe(1)
}) 

 export function computed<T>(getter: () => T): ComputedRef<T>
export function computed<T>(
  options: WritableComputedOptions<T>
): WritableComputedRef<T>
export function computed<T>(
  getterOrOptions: (() => T) | WritableComputedOptions<T>
): any {
  const isReadonly = isFunction(getterOrOptions)
  const getter = isReadonly
    ? (getterOrOptions as (() => T))
    : (getterOrOptions as WritableComputedOptions<T>).get
  const setter = isReadonly
    ? __DEV__
      ? () => {
          console.warn('Write operation failed: computed value is readonly')
        }
      : NOOP
    : (getterOrOptions as WritableComputedOptions<T>).set

  let dirty = true
  let value: T

  const runner = effect(getter, {
    lazy: true,
    // mark effect as computed so that it gets priority during trigger
    computed: true,
    scheduler: () => {
      dirty = true
    }
  }) 

 export function effect(
  fn: Function,
  options: ReactiveEffectOptions = EMPTY_OBJ
): ReactiveEffect {
  if ((fn as ReactiveEffect).isEffect) {
    fn = (fn as ReactiveEffect).raw
  }
  const effect = createReactiveEffect(fn, options)
  if (!options.lazy) {
    effect()
  }
  return effect
} 

 const runner = effect(getter, {
    lazy: true,
    // mark effect as computed so that it gets priority during trigger
    computed: true,
    scheduler: () => {
      dirty = true
    }
  })
  return {
    [refSymbol]: true,
    // expose effect so computed can be stopped
    effect: runner,
    get value() {
      if (dirty) {
        value = runner()
        dirty = false
      }
      // When computed effects are accessed in a parent effect, the parent
      // should track all the dependencies the computed property has tracked.
      // This should also apply for chained computed properties.
      trackChildRun(runner)
      return value
    },
    set value(newValue: T) {
      setter(newValue)
    }
  }
} 

 export function trigger(
  target: any,
  type: OperationTypes,
  key?: string | symbol,
  extraInfo?: any
) {
  const depsMap = targetMap.get(target)
  if (depsMap === void 0) {
    // never been tracked
    return
  }
  const effects = new Set<ReactiveEffect>()
  const computedRunners = new Set<ReactiveEffect>()
  if (type === OperationTypes.CLEAR) {
    // collection being cleared, trigger all effects for target
    depsMap.forEach(dep => {
      addRunners(effects, computedRunners, dep)
    })
  } else {
    // schedule runs for SET | ADD | DELETE
    if (key !== void 0) {
      addRunners(effects, computedRunners, depsMap.get(key))
    }
    // also run for iteration key on ADD | DELETE
    if (type === OperationTypes.ADD || type === OperationTypes.DELETE) {
      const iterationKey = Array.isArray(target) ? 'length' : ITERATE_KEY
      addRunners(effects, computedRunners, depsMap.get(iterationKey))
    }
  }
  const run = (effect: ReactiveEffect) => {
    scheduleRun(effect, target, type, key, extraInfo)
  }
  // Important: computed effects must be run first so that computed getters
  // can be invalidated before any normal effects that depend on them are run.
  computedRunners.forEach(run)
  effects.forEach(run)
}

function addRunners(
  effects: Set<ReactiveEffect>,
  computedRunners: Set<ReactiveEffect>,
  effectsToAdd: Set<ReactiveEffect> | undefined
) {
  if (effectsToAdd !== void 0) {
    effectsToAdd.forEach(effect => {
      if (effect.computed) {
        computedRunners.add(effect)
      } else {
        effects.add(effect)
      }
    })
  }
} 

 it('should work when chained', () => {
    const value = reactive({ foo: 0 })
    const c1 = computed(() => value.foo)
    const c2 = computed(() => c1.value + 1)
    expect(c2.value).toBe(1)
    expect(c1.value).toBe(0)
    value.foo++
    expect(c2.value).toBe(2)
    expect(c1.value).toBe(1)
  }) 

### [](https://hackmd.io/ZfQArpjoQ8GrGqCABYpPpQ?view#Triggered-effect-when-chained "Triggered-effect-when-chained")チェーン時のトリガー効果

次に、一般的なeffectがcomputedに依存する場合に何が起こるかについて説明します。

この例では、依存関係は`effect -> c2 -> c1 -> value`です。effectはlazyではないため、直接実行されます。以下は以前のテキストの順序で表現します。

1.  `push effect, activeReactiveEffectStack => [ effect ]`
2.  `effect run fn // which is dummy = c2.value`
3.  `push c2, activeReactiveEffectStack => [ effect, c2 ]`
4.  `c2 run fn // which is c1.value + 1`
5.  `push c1, activeReactiveEffectStack => [ effect, c2, c1 ]`
6.  `c1 run fn // which is value.foo`
7.  `value 依賴於 activeReactiveEffectStack top // 也就是 c1`
8.  `pop c1, activeReactiveEffectStack => [ effect, c2 ]`
9.  `c1 run trackChildRun，將 activeReactiveEffectStack top 也就是 c2 依賴於 c1 的所有依賴`
10.  `pop c2, activeReactiveEffectStack => [ effect ]`
11.  `c2 run trackChildRun，將 activeReactiveEffectStack top 也就是 effect 依賴於 c2 的所有依賴 (而又此時 c2 擁有 c1 的所有依賴，所以也就是 c1, c2 兩者的所有依賴`
12.  `pop effect, activeReactiveEffectStack => []`

この時点で、dummyは12行目で1になります。`getter1`と`getter2`も一度実行され、次にvalue.foo++が実行され、3つの依存者`effect`、`c2`、`c1`がトリガーされます。そしてもちろん、`computedRunners`と`effects`は集合なので、必ず一度だけ実行され、それぞれの関数がトリガーされます。このテストケースは完了しました。

let dummy
effect(() => {
  dummy = c2.value
})
expect(dummy).toBe(1)
expect(getter1).toHaveBeenCalledTimes(1)
expect(getter2).toHaveBeenCalledTimes(1)
value.foo++
expect(dummy).toBe(2)
// should not result in duplicate calls
expect(getter1).toHaveBeenCalledTimes(2)
expect(getter2).toHaveBeenCalledTimes(2)

これで、computedのすべての状況がどれほど複雑で困難であるかを説明できますが、困難はまだ続きます。このシリーズの記事では、徐々にコアや仮想DOMの方に進んでいきます。