React16源码: React中event事件触发的源码实现

2024-02-03 09:20

本文主要是介绍React16源码: React中event事件触发的源码实现,希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!

event 事件触发过程


1 )概述

  • 在之前事件绑定时,绑定的是两个方法
    • 一个是 dispatchInteractiveEvent
    • 另外一个 dispatchEvent
  • 其实它们调用的方法都是差不多的,一开始会有一点小的区别

2 )源码

定位到 packages/react-dom/src/events/ReactDOMEventListener.js#L165

进入 trapCapturedEvent

export function trapCapturedEvent(topLevelType: DOMTopLevelEventType,element: Document | Element,
) {if (!element) {return null;}// 注意这里,根据是否是 Interactive 类型的事件,调用的不同的回调,最终赋值给 dispatchconst dispatch = isInteractiveTopLevelEventType(topLevelType)? dispatchInteractiveEvent: dispatchEvent;addEventCaptureListener(element,getRawEventName(topLevelType),// Check if interactive and wrap in interactiveUpdates// 这边的topleveltype呢,是我们在进行 dom 的事件绑定的时候已经通过 bind 给它绑定好了// 在绑定事件的时候,就已经确定了一个值, 比如说是onChange这类的toplevel的事件名称dispatch.bind(null, topLevelType),);
}

2.1 先看 dispatchInteractiveEvent

定位到 packages/react-dom/src/events/ReactDOMEventListener.js#L184

// packages/react-dom/src/events/ReactDOMEventListener.js#L184
// nativeEvent,就是我们事件触发的时候,我们的domm的事件体系会给我们一个event对象
// 可以通过它来进入默认行为之类的这么一个事件对象
function dispatchInteractiveEvent(topLevelType, nativeEvent) {interactiveUpdates(dispatchEvent, topLevelType, nativeEvent);
}// packages/events/ReactGenericBatching.js#L55
export function interactiveUpdates(fn, a, b) {return _interactiveUpdatesImpl(fn, a, b);
}// packages/events/ReactGenericBatching.js#L23
let _interactiveUpdatesImpl = function(fn, a, b) {return fn(a, b);
};
  • 可见 dispatchInteractiveEvent 最终还是要调用 dispatchEvent, 只是多包了一层

2.2 进入 dispatchEvent

定位到 packages/react-dom/src/events/ReactDOMEventListener.js#L188

export function dispatchEvent(topLevelType: DOMTopLevelEventType,nativeEvent: AnyNativeEvent,
) {if (!_enabled) {return;}// 注意这里const nativeEventTarget = getEventTarget(nativeEvent);let targetInst = getClosestInstanceFromNode(nativeEventTarget);// 存在 符合条件的,并且没有被挂载if (targetInst !== null &&typeof targetInst.tag === 'number' &&!isFiberMounted(targetInst)) {// If we get an event (ex: img onload) before committing that// component's mount, ignore it for now (that is, treat it as if it was an// event on a non-React tree). We might also consider queueing events and// dispatching them after the mount.targetInst = null; // 这个 target 置空}// 这里只是一个对象,用于携带信息const bookKeeping = getTopLevelCallbackBookKeeping(topLevelType,nativeEvent,targetInst,);try {// Event queue being processed in the same cycle allows// `preventDefault`.batchedUpdates(handleTopLevel, bookKeeping);} finally {releaseTopLevelCallbackBookKeeping(bookKeeping);}
}
  • 首先它要获取 nativeEventTarget,这个 target 就是我们 event 对象上面的 target

  • 它是出于对各种系统的一个兼容调用的一个方法来进行一个 Polyfill

  • 进入这个 getEventTarget 方法

    import {TEXT_NODE} from '../shared/HTMLNodeType';/*** Gets the target node from a native browser event by accounting for* inconsistencies in browser DOM APIs.** @param {object} nativeEvent Native browser event.* @return {DOMEventTarget} Target node.*/
    function getEventTarget(nativeEvent) {// 这个是对 IE9 的兼容// Fallback to nativeEvent.srcElement for IE9// https://github.com/facebook/react/issues/12506let target = nativeEvent.target || nativeEvent.srcElement || window;// Normalize SVG <use> element events #4963if (target.correspondingUseElement) {target = target.correspondingUseElement;}// Safari may fire events on text nodes (Node.TEXT_NODE is 3).// @see http://www.quirksmode.org/js/events_properties.htmlreturn target.nodeType === TEXT_NODE ? target.parentNode : target;
    }
    
    • 这个方法主要是为了兼容浏览器API获取 target 对象, 最终根据是否是 TEXT_NODE 返回 target.parentNode 或 target
  • 进入 getClosestInstanceFromNode

    export function getClosestInstanceFromNode(node) {// 存在,直接 returnif (node[internalInstanceKey]) {return node[internalInstanceKey]; // 这个就是 初始化dom节点的时候,在node上插入这么一个key, 来指定对应的 fiber 对象}// 不存在,一直找 parentNodewhile (!node[internalInstanceKey]) {if (node.parentNode) {node = node.parentNode;} else {// Top of the tree. This node must not be part of a React tree (or is// unmounted, potentially).return null;}}// 这个 inst 就是一个 fiber 对象, 找到是 HostComponent 或 HostText 类型的let inst = node[internalInstanceKey];if (inst.tag === HostComponent || inst.tag === HostText) {// In Fiber, this will always be the deepest root.return inst;}return null;
    }
    
  • 进入 isFiberMounted

    const MOUNTING = 1;
    const MOUNTED = 2;
    const UNMOUNTED = 3;function isFiberMountedImpl(fiber: Fiber): number {let node = fiber;// 不存在,说明是即将插入或没有插入的节点if (!fiber.alternate) {// If there is no alternate, this might be a new tree that isn't inserted// yet. If it is, then it will have a pending insertion effect on it.// 这种是即将要插入的if ((node.effectTag & Placement) !== NoEffect) {return MOUNTING;}// 如果当前不是,向上找父节点,也是即将插入的while (node.return) {node = node.return;if ((node.effectTag & Placement) !== NoEffect) {return MOUNTING;}}} else {// 存在 alternate, 继续向上找while (node.return) {node = node.return;}}// 如果上级存在,并且是 HostRoot 说明已经被挂载了if (node.tag === HostRoot) {// TODO: Check if this was a nested HostRoot when used with// renderContainerIntoSubtree.return MOUNTED;}// If we didn't hit the root, that means that we're in an disconnected tree// that has been unmounted.// 其他情况都是未挂载的return UNMOUNTED;
    }export function isFiberMounted(fiber: Fiber): boolean {return isFiberMountedImpl(fiber) === MOUNTED;
    }
    
  • 进入 getTopLevelCallbackBookKeeping

    // packages/react-dom/src/events/ReactDOMEventListener.js#L50
    const CALLBACK_BOOKKEEPING_POOL_SIZE = 10;
    const callbackBookkeepingPool = [];// Used to store ancestor hierarchy in top level callback
    function getTopLevelCallbackBookKeeping(topLevelType,nativeEvent,targetInst,
    ): {topLevelType: ?DOMTopLevelEventType,nativeEvent: ?AnyNativeEvent,targetInst: Fiber | null,ancestors: Array<Fiber>,
    } {if (callbackBookkeepingPool.length) {const instance = callbackBookkeepingPool.pop();instance.topLevelType = topLevelType;instance.nativeEvent = nativeEvent;instance.targetInst = targetInst;return instance;}return {topLevelType,nativeEvent,targetInst,ancestors: [],};
    }
    
    • 这个函数就是一缓存机制
    • 最终我们在执行完整个react事件之后,会把这个对象再归还到这个pool里面来进行一个存储
    • 让浏览器的js运行环境不去删除这个对象,也让我们在后期不需要去重新创建一个对象,
    • 以减少这个对象声明和对象垃圾回收的一个性能开销
  • 进入 batchedUpdates

    // packages/events/ReactGenericBatching.js#L29
    let _batchedUpdatesImpl = function(fn, bookkeeping) {return fn(bookkeeping);
    };
    let isBatching = false;
    export function batchedUpdates(fn, bookkeeping) {if (isBatching) {// If we are currently inside another batch, we need to wait until it// fully completes before restoring state.return fn(bookkeeping);}isBatching = true;try {return _batchedUpdatesImpl(fn, bookkeeping);} finally {// Here we wait until all updates have propagated, which is important// when using controlled components within layers:// https://github.com/facebook/react/issues/1698// Then we restore state of any controlled component.isBatching = false;// 下面的代码其实就跟 input 控制输入 有关的// 我们知道在 react 当中我们通过 value 给 input 标签上面去绑定了值,直接在外部输入的值// 如果没有 onChange 事件来处理这个 state,它这个值输不进去的,这就是 input的控制输入 的一个概念// 其控制就是在这里实现的const controlledComponentsHavePendingUpdates = needsStateRestore();if (controlledComponentsHavePendingUpdates) {// If a controlled event was fired, we may need to restore the state of// the DOM node back to the controlled value. This is necessary when React// bails out of the update without touching the DOM._flushInteractiveUpdatesImpl();restoreStateIfNeeded();}}
    }// packages/events/ReactControlledComponent.js#L58
    export function needsStateRestore(): boolean {return restoreTarget !== null || restoreQueue !== null;
    }export function restoreStateIfNeeded() {if (!restoreTarget) {return;}const target = restoreTarget;const queuedTargets = restoreQueue;restoreTarget = null;restoreQueue = null;restoreStateOfTarget(target);if (queuedTargets) {for (let i = 0; i < queuedTargets.length; i++) {restoreStateOfTarget(queuedTargets[i]);}}
    }
    
  • batchedUpdates 里面调用的方法是 handleTopLevel

    function handleTopLevel(bookKeeping) {let targetInst = bookKeeping.targetInst;// Loop through the hierarchy, in case there's any nested components.// It's important that we build the array of ancestors before calling any// event handlers, because event handlers can modify the DOM, leading to// inconsistencies with ReactMount's node cache. See #1105.let ancestor = targetInst;do {// 如果不存在,就push,并且跳出循环if (!ancestor) {bookKeeping.ancestors.push(ancestor);break;}// 如果存在了,找到 Root 挂载节点const root = findRootContainerNode(ancestor);// 不存在挂载节点,则跳出if (!root) {break;}// 存在挂载节点bookKeeping.ancestors.push(ancestor);// 这个方法之前已经分析了,找到存储的 fiber 对象// 在这里, 这个时候传入了是这个root,对于大部分情况来讲, HostRoot 已经没有上级的节点,会是处于react的一个应用当中// 也可能是会有这种情况的, 比如通过一些比较 hack 的一些方式, 我们在react应用里面再去渲染了一个新的react应用// 这种方法也可能是存在的,所以在这边就尝试了这么去做// 因为它们两个如果确实出现这种情况,那么它们的root节点是不一样的// 事件正常来讲是要冒泡到最外层的那个root树的最顶上的// 所以这种情况需要去调用这个方法,去把所有的 ancestor 给找到,并且推到这个 bookKeeping.ancestors 里面ancestor = getClosestInstanceFromNode(root); } while (ancestor);// 对于每一个 concest,去获取它的 targetInst 对大部分情况, 其实就是我们这个 targetInst // 就是我们这个事件触发的那一个节点 event.target 对应的那个fiber对象for (let i = 0; i < bookKeeping.ancestors.length; i++) {targetInst = bookKeeping.ancestors[i];runExtractedEventsInBatch(bookKeeping.topLevelType,targetInst,bookKeeping.nativeEvent,getEventTarget(bookKeeping.nativeEvent),);}
    }
    
    • 进入 findRootContainerNode
      function findRootContainerNode(inst) {// TODO: It may be a good idea to cache this to prevent unnecessary DOM// traversal, but caching is difficult to do correctly without using a// mutation observer to listen for all DOM changes.// 向上找while (inst.return) {inst = inst.return;}// 如果不是 HostRoot 则失败if (inst.tag !== HostRoot) {// This can happen if we're in a detached tree.return null;}// 找到 react 应用挂载的 dom节点return inst.stateNode.containerInfo;
      }
      
    • 进入 runExtractedEventsInBatch
      export function runExtractedEventsInBatch(topLevelType: TopLevelType,targetInst: null | Fiber,nativeEvent: AnyNativeEvent,nativeEventTarget: EventTarget,
      ) {// 获取所有事件const events = extractEvents(topLevelType,targetInst,nativeEvent,nativeEventTarget,);runEventsInBatch(events);
      }// 生成事件对象
      function extractEvents(topLevelType: TopLevelType,targetInst: null | Fiber,nativeEvent: AnyNativeEvent,nativeEventTarget: EventTarget,
      ): Array<ReactSyntheticEvent> | ReactSyntheticEvent | null {let events = null;// 调用每一个plugin, 在内部,调用 possiblePlugin.extractEventsfor (let i = 0; i < plugins.length; i++) {// Not every plugin in the ordering may be loaded at runtime.const possiblePlugin: PluginModule<AnyNativeEvent> = plugins[i];if (possiblePlugin) {const extractedEvents = possiblePlugin.extractEvents(topLevelType,targetInst,nativeEvent,nativeEventTarget,);// 如果存在,则插入到对象中if (extractedEvents) {events = accumulateInto(events, extractedEvents);}}}return events;
      }let eventQueue: ?(Array<ReactSyntheticEvent> | ReactSyntheticEvent) = null;
      export function runEventsInBatch(events: Array<ReactSyntheticEvent> | ReactSyntheticEvent | null,
      ) {if (events !== null) {eventQueue = accumulateInto(eventQueue, events);}// Set `eventQueue` to null before processing it so that we can tell if more// events get enqueued while processing.const processingEventQueue = eventQueue;eventQueue = null;if (!processingEventQueue) {return;}// 对这个 processingEventQueue, 可能是数组,也可能只有一个event的这个内容// 对它调用了这个 executeDispatchesAndReleaseTopLevel 方法forEachAccumulated(processingEventQueue, executeDispatchesAndReleaseTopLevel);invariant(!eventQueue,'processEventQueue(): Additional events were enqueued while processing ' +'an event queue. Support for this has not yet been implemented.',);// This would be a good time to rethrow if any of the event handlers threw.rethrowCaughtError();
      }
      
      • 进入 accumulateInto
        // 把两个值(数组)合并,形成一个数组
        function accumulateInto<T>(current: ?(Array<T> | T),next: T | Array<T>,
        ): T | Array<T> {invariant(next != null,'accumulateInto(...): Accumulated items must not be null or undefined.',);if (current == null) {return next;}// Both are not empty. Warning: Never call x.concat(y) when you are not// certain that x is an Array (x could be a string with concat method).// 合并两个数组if (Array.isArray(current)) {if (Array.isArray(next)) {current.push.apply(current, next);return current;}current.push(next);return current;}if (Array.isArray(next)) {// A bit too dangerous to mutate `next`.return [current].concat(next);}return [current, next];
        }
        
      • 进入 forEachAccumulated
        // 对于传进来的一个数组,判断它是否是一个数组
        // 如果是数组就会去对每一项调用这个 callback
        // 如果它不是一个数组,就直接调用这个callback传入这个值就可以了
        function forEachAccumulated<T>(arr: ?(Array<T> | T),cb: (elem: T) => void,scope: ?any,
        ) {if (Array.isArray(arr)) {arr.forEach(cb, scope);} else if (arr) {cb.call(scope, arr);}
        }
        
      • 进入 executeDispatchesAndReleaseTopLevel
        const executeDispatchesAndReleaseTopLevel = function(e) {return executeDispatchesAndRelease(e);
        };const executeDispatchesAndRelease = function(event: ReactSyntheticEvent) {if (event) {executeDispatchesInOrder(event);if (!event.isPersistent()) {event.constructor.release(event);}}
        };// packages/events/EventPluginUtils.js#L76
        // 最后真正调用这个事件的地方,其实它里面整个过程会非常的复杂,有各种各样的函数的嵌套调用
        // 其实里面可能有将近一半的函数都是工具类型的函数,注意阅读代码时,别被绕进去
        export function executeDispatchesInOrder(event) {// 这边获取了 dispatchListeners 以及 dispatchInstances 这两个数据// 这两个数据都来自 event 对象,上面会挂载了一个叫 _dispatchListeners 和 _dispatchInstances// 这两个东西都是数组,并且是一一对应的关系const dispatchListeners = event._dispatchListeners;const dispatchInstances = event._dispatchInstances;// 忽略if (__DEV__) {validateEventDispatches(event);}// 然后,它去判断一下是否是一个数组, 如果是一个数组对它进行一个遍历if (Array.isArray(dispatchListeners)) {for (let i = 0; i < dispatchListeners.length; i++) {// 并且判断一下 event 是否已经 isPropagationStopped,就是我们已经停止冒泡了// 如果是的话,我们就直接 breakif (event.isPropagationStopped()) {break;}// Listeners and Instances are two parallel arrays that are always in sync.executeDispatch(event, dispatchListeners[i], dispatchInstances[i]);}// 不是数组,但是存在} else if (dispatchListeners) {// 调用这个方法executeDispatch(event, dispatchListeners, dispatchInstances);}// 重置event._dispatchListeners = null;event._dispatchInstances = null;
        }
        
        • 进入 executeDispatch
          function executeDispatch(event, listener, inst) {const type = event.type || 'unknown-event';event.currentTarget = getNodeFromInstance(inst); // 从 inst 上获取 node 节点invokeGuardedCallbackAndCatchFirstError(type, listener, undefined, event); // 这里回调最终被触发调用event.currentTarget = null;
          }
          
          • 进入 invokeGuardedCallbackAndCatchFirstError
            // packages/shared/ReactErrorUtils.js#L67
            export function invokeGuardedCallbackAndCatchFirstError<A,B,C,D,E,F,Context,
            >(name: string | null,func: (a: A, b: B, c: C, d: D, e: E, f: F) => void,context: Context,a: A,b: B,c: C,d: D,e: E,f: F,
            ): void {// 这个函数之前遇到过,目前不再展开invokeGuardedCallback.apply(this, arguments);if (hasError) {const error = clearCaughtError();if (!hasRethrowError) {hasRethrowError = true;rethrowError = error;}}
            }
            
  • 到这里为止,这边的 listener 就已经被调用了

  • 我们真正的每一个节点上面,如果有绑定这个事件,它就会调用它的一个回调

  • 这就是事件触发的整个流程, 非常的繁琐,有各种各样的方法,嵌套的调用

这篇关于React16源码: React中event事件触发的源码实现的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!



http://www.chinasem.cn/article/673684

相关文章

分布式锁在Spring Boot应用中的实现过程

《分布式锁在SpringBoot应用中的实现过程》文章介绍在SpringBoot中通过自定义Lock注解、LockAspect切面和RedisLockUtils工具类实现分布式锁,确保多实例并发操作... 目录Lock注解LockASPect切面RedisLockUtils工具类总结在现代微服务架构中,分布

Java使用Thumbnailator库实现图片处理与压缩功能

《Java使用Thumbnailator库实现图片处理与压缩功能》Thumbnailator是高性能Java图像处理库,支持缩放、旋转、水印添加、裁剪及格式转换,提供易用API和性能优化,适合Web应... 目录1. 图片处理库Thumbnailator介绍2. 基本和指定大小图片缩放功能2.1 图片缩放的

Python使用Tenacity一行代码实现自动重试详解

《Python使用Tenacity一行代码实现自动重试详解》tenacity是一个专为Python设计的通用重试库,它的核心理念就是用简单、清晰的方式,为任何可能失败的操作添加重试能力,下面我们就来看... 目录一切始于一个简单的 API 调用Tenacity 入门:一行代码实现优雅重试精细控制:让重试按我

Redis客户端连接机制的实现方案

《Redis客户端连接机制的实现方案》本文主要介绍了Redis客户端连接机制的实现方案,包括事件驱动模型、非阻塞I/O处理、连接池应用及配置优化,具有一定的参考价值,感兴趣的可以了解一下... 目录1. Redis连接模型概述2. 连接建立过程详解2.1 连php接初始化流程2.2 关键配置参数3. 最大连

Python实现网格交易策略的过程

《Python实现网格交易策略的过程》本文讲解Python网格交易策略,利用ccxt获取加密货币数据及backtrader回测,通过设定网格节点,低买高卖获利,适合震荡行情,下面跟我一起看看我们的第一... 网格交易是一种经典的量化交易策略,其核心思想是在价格上下预设多个“网格”,当价格触发特定网格时执行买

python设置环境变量路径实现过程

《python设置环境变量路径实现过程》本文介绍设置Python路径的多种方法:临时设置(Windows用`set`,Linux/macOS用`export`)、永久设置(系统属性或shell配置文件... 目录设置python路径的方法临时设置环境变量(适用于当前会话)永久设置环境变量(Windows系统

Python对接支付宝支付之使用AliPay实现的详细操作指南

《Python对接支付宝支付之使用AliPay实现的详细操作指南》支付宝没有提供PythonSDK,但是强大的github就有提供python-alipay-sdk,封装里很多复杂操作,使用这个我们就... 目录一、引言二、准备工作2.1 支付宝开放平台入驻与应用创建2.2 密钥生成与配置2.3 安装ali

Spring Security 单点登录与自动登录机制的实现原理

《SpringSecurity单点登录与自动登录机制的实现原理》本文探讨SpringSecurity实现单点登录(SSO)与自动登录机制,涵盖JWT跨系统认证、RememberMe持久化Token... 目录一、核心概念解析1.1 单点登录(SSO)1.2 自动登录(Remember Me)二、代码分析三、

PyCharm中配置PyQt的实现步骤

《PyCharm中配置PyQt的实现步骤》PyCharm是JetBrains推出的一款强大的PythonIDE,结合PyQt可以进行pythion高效开发桌面GUI应用程序,本文就来介绍一下PyCha... 目录1. 安装China编程PyQt1.PyQt 核心组件2. 基础 PyQt 应用程序结构3. 使用 Q

Python实现批量提取BLF文件时间戳

《Python实现批量提取BLF文件时间戳》BLF(BinaryLoggingFormat)作为Vector公司推出的CAN总线数据记录格式,被广泛用于存储车辆通信数据,本文将使用Python轻松提取... 目录一、为什么需要批量处理 BLF 文件二、核心代码解析:从文件遍历到数据导出1. 环境准备与依赖库