From: Evan You <yyx990803@gmail.com>
Date: Wed, 19 Aug 2020 22:02:17 +0000 (-0400)
Subject: chore: comments
X-Git-Tag: v3.0.0-rc.6~1
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=cfa7636bbe841d8f7e72b708e96cf0eefdc85b92;p=thirdparty%2Fvuejs%2Fcore.git

chore: comments
---

diff --git a/packages/runtime-core/src/scheduler.ts b/packages/runtime-core/src/scheduler.ts
index db8051b207..9120c3bf17 100644
--- a/packages/runtime-core/src/scheduler.ts
+++ b/packages/runtime-core/src/scheduler.ts
@@ -12,12 +12,13 @@ export interface SchedulerJob {
    * By default, a job cannot trigger itself because some built-in method calls,
    * e.g. Array.prototype.push actually performs reads as well (#1740) which
    * can lead to confusing infinite loops.
-   * The allowed cases are component render functions and watch callbacks.
-   * Render functions may update child component props, which in turn trigger
-   * flush: "pre" watch callbacks that mutates state that the parent relies on
-   * (#1801). Watch callbacks doesn't track its dependencies so if it triggers
-   * itself again, it's likely intentional and it is the user's responsibility
-   * to perform recursive state mutation that eventually stabilizes (#1727).
+   * The allowed cases are component update functions and watch callbacks.
+   * Component update functions may update child component props, which in turn
+   * trigger flush: "pre" watch callbacks that mutates state that the parent
+   * relies on (#1801). Watch callbacks doesn't track its dependencies so if it
+   * triggers itself again, it's likely intentional and it is the user's
+   * responsibility to perform recursive state mutation that eventually
+   * stabilizes (#1727).
    */
   allowRecurse?: boolean
 }