理解Vue 2.5的Diff算法
DOM“天生就慢”,所以前端各大框架都提供了對(duì)DOM操作進(jìn)行優(yōu)化的辦法,Angular中的是臟值檢查,React首先提出了Virtual Dom,Vue2.0也加入了Virtual Dom,與React類(lèi)似。
本文將對(duì)于Vue 2.5.3版本中使用的Virtual Dom進(jìn)行分析。
updataChildren是Diff算法的核心,所以本文對(duì)updataChildren進(jìn)行了圖文的分析。
1.VNode對(duì)象
一個(gè)VNode的實(shí)例包含了以下屬性,這部分代碼在src/core/vdom/vnode.js里
export default class VNode {tag: string | void;data: VNodeData | void;children: ?Array<VNode>;text: string | void;elm: Node | void;ns: string | void;context: Component | void; // rendered in this component's scopekey: string | number | void;componentOptions: VNodeComponentOptions | void;componentInstance: Component | void; // component instanceparent: VNode | void; // component placeholder node// strictly internalraw: boolean; // contains raw HTML? (server only)isStatic: boolean; // hoisted static nodeisRootInsert: boolean; // necessary for enter transition checkisComment: boolean; // empty comment placeholder?isCloned: boolean; // is a cloned node?isOnce: boolean; // is a v-once node?asyncFactory: Function | void; // async component factory functionasyncMeta: Object | void;isAsyncPlaceholder: boolean;ssrContext: Object | void;functionalContext: Component | void; // real context vm for functional nodesfunctionalOptions: ?ComponentOptions; // for SSR cachingfunctionalScopeId: ?string; // functioanl scope id support- tag: 當(dāng)前節(jié)點(diǎn)的標(biāo)簽名
- data: 當(dāng)前節(jié)點(diǎn)的數(shù)據(jù)對(duì)象,具體包含哪些字段可以參考vue源碼types/vnode.d.ts中對(duì)VNodeData的定義
- children: 數(shù)組類(lèi)型,包含了當(dāng)前節(jié)點(diǎn)的子節(jié)點(diǎn)
- text: 當(dāng)前節(jié)點(diǎn)的文本,一般文本節(jié)點(diǎn)或注釋節(jié)點(diǎn)會(huì)有該屬性
- elm: 當(dāng)前虛擬節(jié)點(diǎn)對(duì)應(yīng)的真實(shí)的dom節(jié)點(diǎn)
- ns: 節(jié)點(diǎn)的namespace
- context: 編譯作用域
- functionalContext: 函數(shù)化組件的作用域
- key: 節(jié)點(diǎn)的key屬性,用于作為節(jié)點(diǎn)的標(biāo)識(shí),有利于patch的優(yōu)化
- componentOptions: 創(chuàng)建組件實(shí)例時(shí)會(huì)用到的選項(xiàng)信息
- child: 當(dāng)前節(jié)點(diǎn)對(duì)應(yīng)的組件實(shí)例
- parent: 組件的占位節(jié)點(diǎn)
- raw: raw html
- isStatic: 靜態(tài)節(jié)點(diǎn)的標(biāo)識(shí)
- isRootInsert: 是否作為根節(jié)點(diǎn)插入,被包裹的節(jié)點(diǎn),該屬性的值為false
- isComment: 當(dāng)前節(jié)點(diǎn)是否是注釋節(jié)點(diǎn)
- isCloned: 當(dāng)前節(jié)點(diǎn)是否為克隆節(jié)點(diǎn)
- isOnce: 當(dāng)前節(jié)點(diǎn)是否有v-once指令
2.VNode的分類(lèi)
VNode可以理解為VueVirtual Dom的一個(gè)基類(lèi),通過(guò)VNode構(gòu)造函數(shù)生成的VNnode實(shí)例可為如下幾類(lèi):
- EmptyVNode: 沒(méi)有內(nèi)容的注釋節(jié)點(diǎn)
- TextVNode: 文本節(jié)點(diǎn)
- ElementVNode: 普通元素節(jié)點(diǎn)
- ComponentVNode: 組件節(jié)點(diǎn)
- CloneVNode: 克隆節(jié)點(diǎn),可以是以上任意類(lèi)型的節(jié)點(diǎn),唯一的區(qū)別在于isCloned屬性為true
3.Create-Element源碼解析
這部分代碼在src/core/vdom/create-element.js里,我就直接粘代碼加上我的注釋了
export function createElement (context: Component,tag: any,data: any,children: any,normalizationType: any,alwaysNormalize: boolean ): VNode {// 兼容不傳data的情況if (Array.isArray(data) || isPrimitive(data)) {normalizationType = childrenchildren = datadata = undefined}// 如果alwaysNormalize是true// 那么normalizationType應(yīng)該設(shè)置為常量ALWAYS_NORMALIZE的值if (isTrue(alwaysNormalize)) {normalizationType = ALWAYS_NORMALIZE}// 調(diào)用_createElement創(chuàng)建虛擬節(jié)點(diǎn)return _createElement(context, tag, data, children, normalizationType) }export function _createElement (context: Component,tag?: string | Class<Component> | Function | Object,data?: VNodeData,children?: any,normalizationType?: number ): VNode {/*** 如果存在data.__ob__,說(shuō)明data是被Observer觀察的數(shù)據(jù)* 不能用作虛擬節(jié)點(diǎn)的data* 需要拋出警告,并返回一個(gè)空節(jié)點(diǎn)** 被監(jiān)控的data不能被用作vnode渲染的數(shù)據(jù)的原因是:* data在vnode渲染過(guò)程中可能會(huì)被改變,這樣會(huì)觸發(fā)監(jiān)控,導(dǎo)致不符合預(yù)期的操作*/if (isDef(data) && isDef((data: any).__ob__)) {process.env.NODE_ENV !== 'production' && warn(`Avoid using observed data object as vnode data: ${JSON.stringify(data)}\n` +'Always create fresh vnode data objects in each render!',context)return createEmptyVNode()}// object syntax in v-bindif (isDef(data) && isDef(data.is)) {tag = data.is}if (!tag) {// 當(dāng)組件的is屬性被設(shè)置為一個(gè)falsy的值// Vue將不會(huì)知道要把這個(gè)組件渲染成什么// 所以渲染一個(gè)空節(jié)點(diǎn)// in case of component :is set to falsy valuereturn createEmptyVNode()}// key為非原始值警告// warn against non-primitive keyif (process.env.NODE_ENV !== 'production' &&isDef(data) && isDef(data.key) && !isPrimitive(data.key)) {warn('Avoid using non-primitive value as key, ' +'use string/number value instead.',context)}// 作用域插槽// support single function children as default scoped slotif (Array.isArray(children) &&typeof children[0] === 'function') {data = data || {}data.scopedSlots = { default: children[0] }children.length = 0}// 根據(jù)normalizationType的值,選擇不同的處理方法if (normalizationType === ALWAYS_NORMALIZE) {children = normalizeChildren(children)} else if (normalizationType === SIMPLE_NORMALIZE) {children = simpleNormalizeChildren(children)}let vnode, ns// 如果標(biāo)簽名是字符串類(lèi)型if (typeof tag === 'string') {let Ctor// 獲取標(biāo)簽的命名空間ns = (context.$vnode && context.$vnode.ns) || config.getTagNamespace(tag)// 如果是保留標(biāo)簽if (config.isReservedTag(tag)) {// platform built-in elements// 就創(chuàng)建這樣一個(gè)vnodevnode = new VNode(config.parsePlatformTagName(tag), data, children,undefined, undefined, context)// 如果不是保留字標(biāo)簽,嘗試從vm的components上查找是否有這個(gè)標(biāo)簽的定義} else if (isDef(Ctor = resolveAsset(context.$options, 'components', tag))) {// component// 如果找到,就創(chuàng)建虛擬組件節(jié)點(diǎn)vnode = createComponent(Ctor, data, context, children, tag)} else {// unknown or unlisted namespaced elements// check at runtime because it may get assigned a namespace when its// parent normalizes children// 兜底方案,創(chuàng)建一個(gè)正常的vnodevnode = new VNode(tag, data, children,undefined, undefined, context)}} else {// 當(dāng)tag不是字符串的時(shí)候,我們認(rèn)為tag是組件的構(gòu)造類(lèi)// 所以直接創(chuàng)建// direct component options / constructorvnode = createComponent(tag, data, context, children)}if (isDef(vnode)) {// 應(yīng)用命名空間if (ns) applyNS(vnode, ns)return vnode} else {// 返回一個(gè)空節(jié)點(diǎn)return createEmptyVNode()} }function applyNS (vnode, ns, force) {vnode.ns = nsif (vnode.tag === 'foreignObject') {// use default namespace inside foreignObjectns = undefinedforce = true}if (isDef(vnode.children)) {for (let i = 0, l = vnode.children.length; i < l; i++) {const child = vnode.children[i]if (isDef(child.tag) && (isUndef(child.ns) || isTrue(force))) {applyNS(child, ns, force)}}} }4.Patch原理
patch函數(shù)的定義在src/core/vdom/patch.js中,patch邏輯比較簡(jiǎn)單,就不粘代碼了
patch函數(shù)接收6個(gè)參數(shù):
- oldVnode: 舊的虛擬節(jié)點(diǎn)或舊的真實(shí)dom節(jié)點(diǎn)
- vnode: 新的虛擬節(jié)點(diǎn)
- hydrating: 是否要跟真是dom混合
- removeOnly: 特殊flag,用于組件
- parentElm: 父節(jié)點(diǎn)
- refElm: 新節(jié)點(diǎn)將插入到refElm之前
patch的邏輯是:
else 當(dāng)vnode和oldVnode都存在時(shí)
- if oldVnode和vnode是同一個(gè)節(jié)點(diǎn),就調(diào)用patchVnode來(lái)進(jìn)行patch
- 當(dāng)vnode和oldVnode不是同一個(gè)節(jié)點(diǎn)時(shí),如果oldVnode是真實(shí)dom節(jié)點(diǎn)或hydrating設(shè)置為true,需要用hydrate函數(shù)將虛擬dom和真是dom進(jìn)行映射,然后將oldVnode設(shè)置為對(duì)應(yīng)的虛擬dom,找到oldVnode.elm的父節(jié)點(diǎn),根據(jù)vnode創(chuàng)建一個(gè)真實(shí)dom節(jié)點(diǎn)并插入到該父節(jié)點(diǎn)中oldVnode.elm的位置
patchVnode的邏輯是:
否則,如果vnode不是文本節(jié)點(diǎn)或注釋節(jié)點(diǎn)
- 如果oldVnode和vnode都有子節(jié)點(diǎn),且2方的子節(jié)點(diǎn)不完全一致,就執(zhí)行updateChildren
- 如果只有oldVnode有子節(jié)點(diǎn),那就把這些節(jié)點(diǎn)都刪除
- 如果只有vnode有子節(jié)點(diǎn),那就創(chuàng)建這些子節(jié)點(diǎn)
- 如果oldVnode和vnode都沒(méi)有子節(jié)點(diǎn),但是oldVnode是文本節(jié)點(diǎn)或注釋節(jié)點(diǎn),就把vnode.elm的文本設(shè)置為空字符串
如果vnode是文本節(jié)點(diǎn)或注釋節(jié)點(diǎn),但是vnode.text != oldVnode.text時(shí),只需要更新vnode.elm的文本內(nèi)容就可以
代碼如下:
function patchVnode (oldVnode, vnode, insertedVnodeQueue, removeOnly) {// 如果新舊節(jié)點(diǎn)一致,什么都不做if (oldVnode === vnode) {return}// 讓vnode.el引用到現(xiàn)在的真實(shí)dom,當(dāng)el修改時(shí),vnode.el會(huì)同步變化const elm = vnode.elm = oldVnode.elm// 異步占位符if (isTrue(oldVnode.isAsyncPlaceholder)) {if (isDef(vnode.asyncFactory.resolved)) {hydrate(oldVnode.elm, vnode, insertedVnodeQueue)} else {vnode.isAsyncPlaceholder = true}return}// reuse element for static trees.// note we only do this if the vnode is cloned -// if the new node is not cloned it means the render functions have been// reset by the hot-reload-api and we need to do a proper re-render.// 如果新舊都是靜態(tài)節(jié)點(diǎn),并且具有相同的key// 當(dāng)vnode是克隆節(jié)點(diǎn)或是v-once指令控制的節(jié)點(diǎn)時(shí),只需要把oldVnode.elm和oldVnode.child都復(fù)制到vnode上// 也不用再有其他操作if (isTrue(vnode.isStatic) &&isTrue(oldVnode.isStatic) &&vnode.key === oldVnode.key &&(isTrue(vnode.isCloned) || isTrue(vnode.isOnce))) {vnode.componentInstance = oldVnode.componentInstancereturn}let iconst data = vnode.dataif (isDef(data) && isDef(i = data.hook) && isDef(i = i.prepatch)) {i(oldVnode, vnode)}const oldCh = oldVnode.childrenconst ch = vnode.childrenif (isDef(data) && isPatchable(vnode)) {for (i = 0; i < cbs.update.length; ++i) cbs.update[i](oldVnode, vnode)if (isDef(i = data.hook) && isDef(i = i.update)) i(oldVnode, vnode)}// 如果vnode不是文本節(jié)點(diǎn)或者注釋節(jié)點(diǎn)if (isUndef(vnode.text)) {// 并且都有子節(jié)點(diǎn)if (isDef(oldCh) && isDef(ch)) {// 并且子節(jié)點(diǎn)不完全一致,則調(diào)用updateChildrenif (oldCh !== ch) updateChildren(elm, oldCh, ch, insertedVnodeQueue, removeOnly)// 如果只有新的vnode有子節(jié)點(diǎn)} else if (isDef(ch)) {if (isDef(oldVnode.text)) nodeOps.setTextContent(elm, '')// elm已經(jīng)引用了老的dom節(jié)點(diǎn),在老的dom節(jié)點(diǎn)上添加子節(jié)點(diǎn)addVnodes(elm, null, ch, 0, ch.length - 1, insertedVnodeQueue)// 如果新vnode沒(méi)有子節(jié)點(diǎn),而vnode有子節(jié)點(diǎn),直接刪除老的oldCh} else if (isDef(oldCh)) {removeVnodes(elm, oldCh, 0, oldCh.length - 1)// 如果老節(jié)點(diǎn)是文本節(jié)點(diǎn)} else if (isDef(oldVnode.text)) {nodeOps.setTextContent(elm, '')}// 如果新vnode和老vnode是文本節(jié)點(diǎn)或注釋節(jié)點(diǎn)// 但是vnode.text != oldVnode.text時(shí),只需要更新vnode.elm的文本內(nèi)容就可以} else if (oldVnode.text !== vnode.text) {nodeOps.setTextContent(elm, vnode.text)}if (isDef(data)) {if (isDef(i = data.hook) && isDef(i = i.postpatch)) i(oldVnode, vnode)}}5.updataChildren原理
updateChildren的邏輯是:
具體代碼如下:
function updateChildren (parentElm, oldCh, newCh, insertedVnodeQueue, removeOnly) {let oldStartIdx = 0 // 舊頭索引let newStartIdx = 0 // 新頭索引let oldEndIdx = oldCh.length - 1 // 舊尾索引let newEndIdx = newCh.length - 1 // 新尾索引let oldStartVnode = oldCh[0] // oldVnode的第一個(gè)childlet oldEndVnode = oldCh[oldEndIdx] // oldVnode的最后一個(gè)childlet newStartVnode = newCh[0] // newVnode的第一個(gè)childlet newEndVnode = newCh[newEndIdx] // newVnode的最后一個(gè)childlet oldKeyToIdx, idxInOld, vnodeToMove, refElm// removeOnly is a special flag used only by <transition-group>// to ensure removed elements stay in correct relative positions// during leaving transitionsconst canMove = !removeOnly// 如果oldStartVnode和oldEndVnode重合,并且新的也都重合了,證明diff完了,循環(huán)結(jié)束while (oldStartIdx <= oldEndIdx && newStartIdx <= newEndIdx) {// 如果oldVnode的第一個(gè)child不存在if (isUndef(oldStartVnode)) {// oldStart索引右移oldStartVnode = oldCh[++oldStartIdx] // Vnode has been moved left// 如果oldVnode的最后一個(gè)child不存在} else if (isUndef(oldEndVnode)) {// oldEnd索引左移oldEndVnode = oldCh[--oldEndIdx]// oldStartVnode和newStartVnode是同一個(gè)節(jié)點(diǎn)} else if (sameVnode(oldStartVnode, newStartVnode)) {// patch oldStartVnode和newStartVnode, 索引左移,繼續(xù)循環(huán)patchVnode(oldStartVnode, newStartVnode, insertedVnodeQueue)oldStartVnode = oldCh[++oldStartIdx]newStartVnode = newCh[++newStartIdx]// oldEndVnode和newEndVnode是同一個(gè)節(jié)點(diǎn)} else if (sameVnode(oldEndVnode, newEndVnode)) {// patch oldEndVnode和newEndVnode,索引右移,繼續(xù)循環(huán)patchVnode(oldEndVnode, newEndVnode, insertedVnodeQueue)oldEndVnode = oldCh[--oldEndIdx]newEndVnode = newCh[--newEndIdx]// oldStartVnode和newEndVnode是同一個(gè)節(jié)點(diǎn)} else if (sameVnode(oldStartVnode, newEndVnode)) { // Vnode moved right// patch oldStartVnode和newEndVnodepatchVnode(oldStartVnode, newEndVnode, insertedVnodeQueue)// 如果removeOnly是false,則將oldStartVnode.eml移動(dòng)到oldEndVnode.elm之后canMove && nodeOps.insertBefore(parentElm, oldStartVnode.elm, nodeOps.nextSibling(oldEndVnode.elm))// oldStart索引右移,newEnd索引左移oldStartVnode = oldCh[++oldStartIdx]newEndVnode = newCh[--newEndIdx]// 如果oldEndVnode和newStartVnode是同一個(gè)節(jié)點(diǎn)} else if (sameVnode(oldEndVnode, newStartVnode)) { // Vnode moved left// patch oldEndVnode和newStartVnodepatchVnode(oldEndVnode, newStartVnode, insertedVnodeQueue)// 如果removeOnly是false,則將oldEndVnode.elm移動(dòng)到oldStartVnode.elm之前canMove && nodeOps.insertBefore(parentElm, oldEndVnode.elm, oldStartVnode.elm)// oldEnd索引左移,newStart索引右移oldEndVnode = oldCh[--oldEndIdx]newStartVnode = newCh[++newStartIdx]// 如果都不匹配} else {if (isUndef(oldKeyToIdx)) oldKeyToIdx = createKeyToOldIdx(oldCh, oldStartIdx, oldEndIdx)// 嘗試在oldChildren中尋找和newStartVnode的具有相同的key的VnodeidxInOld = isDef(newStartVnode.key)? oldKeyToIdx[newStartVnode.key]: findIdxInOld(newStartVnode, oldCh, oldStartIdx, oldEndIdx)// 如果未找到,說(shuō)明newStartVnode是一個(gè)新的節(jié)點(diǎn)if (isUndef(idxInOld)) { // New element// 創(chuàng)建一個(gè)新VnodecreateElm(newStartVnode, insertedVnodeQueue, parentElm, oldStartVnode.elm)// 如果找到了和newStartVnodej具有相同的key的Vnode,叫vnodeToMove} else {vnodeToMove = oldCh[idxInOld]/* istanbul ignore if */if (process.env.NODE_ENV !== 'production' && !vnodeToMove) {warn('It seems there are duplicate keys that is causing an update error. ' +'Make sure each v-for item has a unique key.')}// 比較兩個(gè)具有相同的key的新節(jié)點(diǎn)是否是同一個(gè)節(jié)點(diǎn)//不設(shè)key,newCh和oldCh只會(huì)進(jìn)行頭尾兩端的相互比較,設(shè)key后,除了頭尾兩端的比較外,還會(huì)從用key生成的對(duì)象oldKeyToIdx中查找匹配的節(jié)點(diǎn),所以為節(jié)點(diǎn)設(shè)置key可以更高效的利用dom。if (sameVnode(vnodeToMove, newStartVnode)) {// patch vnodeToMove和newStartVnodepatchVnode(vnodeToMove, newStartVnode, insertedVnodeQueue)// 清除oldCh[idxInOld] = undefined// 如果removeOnly是false,則將找到的和newStartVnodej具有相同的key的Vnode,叫vnodeToMove.elm// 移動(dòng)到oldStartVnode.elm之前canMove && nodeOps.insertBefore(parentElm, vnodeToMove.elm, oldStartVnode.elm)// 如果key相同,但是節(jié)點(diǎn)不相同,則創(chuàng)建一個(gè)新的節(jié)點(diǎn)} else {// same key but different element. treat as new elementcreateElm(newStartVnode, insertedVnodeQueue, parentElm, oldStartVnode.elm)}}// 右移newStartVnode = newCh[++newStartIdx]}}6.具體的Diff分析
不設(shè)key,newCh和oldCh只會(huì)進(jìn)行頭尾兩端的相互比較,設(shè)key后,除了頭尾兩端的比較外,還會(huì)從用key生成的對(duì)象oldKeyToIdx中查找匹配的節(jié)點(diǎn),所以為節(jié)點(diǎn)設(shè)置key可以更高效的利用dom。
diff的遍歷過(guò)程中,只要是對(duì)dom進(jìn)行的操作都調(diào)用api.insertBefore,api.insertBefore只是原生insertBefore的簡(jiǎn)單封裝。
比較分為兩種,一種是有vnode.key的,一種是沒(méi)有的。但這兩種比較對(duì)真實(shí)dom的操作是一致的。
對(duì)于與sameVnode(oldStartVnode, newStartVnode)和sameVnode(oldEndVnode,newEndVnode)為true的情況,不需要對(duì)dom進(jìn)行移動(dòng)。
總結(jié)遍歷過(guò)程,有3種dom操作:上述圖中都有
在結(jié)束時(shí),分為兩種情況:
如果referenceElement為null則newElement將被插入到子節(jié)點(diǎn)的末尾。如果newElement已經(jīng)在DOM樹(shù)中,newElement首先會(huì)從DOM樹(shù)中移除。所以before為null,newElement將被插入到子節(jié)點(diǎn)的末尾。
轉(zhuǎn)載于:https://www.cnblogs.com/isLiu/p/7909889.html
與50位技術(shù)專(zhuān)家面對(duì)面20年技術(shù)見(jiàn)證,附贈(zèng)技術(shù)全景圖總結(jié)
以上是生活随笔為你收集整理的理解Vue 2.5的Diff算法的全部?jī)?nèi)容,希望文章能夠幫你解決所遇到的問(wèn)題。