virtual-scroller 1.11.2 → 1.12.0

package/source/react/useState.js

@@ -1,99 +1,187 @@
-import { useState, useRef, useCallback, useLayoutEffect } from 'react'
+import log, { isDebug } from '../utility/debug.js'
+import getStateSnapshot from '../utility/getStateSnapshot.js'
+
+import { useState, useRef, useCallback, useLayoutEffect, useInsertionEffect } from 'react'
 
 // Creates state management functions.
 export default function _useState({
 	initialState,
 	onRender,
-	itemsProperty,
-	USE_ITEMS_UPDATE_NO_SECOND_RENDER_OPTIMIZATION
+	itemsProperty
 }) {
-	// This is a utility state variable that is used to re-render the component.
-	// It should not be used to access the current `VirtualScroller` state.
-	// It's more of a "requested" `VirtualScroller` state.
-	//
-	// It will also be stale in cases when `USE_ITEMS_UPDATE_NO_SECOND_RENDER_OPTIMIZATION`
-	// feature is used for setting new `items` in state.
-	//
+	// This is a state variable that is used to re-render the component.
+	// Right after the component has finished re-rendering,
+	// `VirtualScroller` state gets updated from this variable.
+	// The reason for that is that `VirtualScroller` state must always
+	// correspond exactly to what's currently rendered on the screen.
 	const [_newState, _setNewState] = useState(initialState)
 
 	// This `state` reference is what `VirtualScroller` uses internally.
 	// It's the "source of truth" on the actual `VirtualScroller` state.
 	const state = useRef(initialState)
 
+	const getState = useCallback(() => {
+		return state.current
+	}, [])
+
 	const setState = useCallback((newState) => {
 		state.current = newState
 	}, [])
 
-	// Accumulates all "pending" state updates until they have been applied.
-	const nextState = useRef(initialState)
+	// Updating of the actual `VirtualScroller` state is done in a
+	// `useInsertionEffect()` rather than in a `useLayoutEffect()`.
+	//
+	// The reason is that using `useLayoutEffect()` would result in
+	// "breaking" the `<VirtualScroller/>` when an `itemComponent`
+	// called `onHeightDidChange()` from its own `useLayoutEffect()`.
+	// In those cases, the `itemCompoent`'s effect would run before
+	// the `<VirtualScroller/>`'s effect, resulting in
+	// `VirtualScroller.onItemHeightDidChange(i)` being run at a moment in time
+	// when the DOM has already been updated for the next `VirtualScroller` state
+	// but the actual `VirtualScroller` state is still a previous ("stale") one
+	// containing "stale" first/last shown item indexes, which would result in an
+	// "index out of bounds" error when `onItemHeightDidChange(i)` tries to access
+	// and measure the DOM element from item index `i` which doesn't already/yet exist.
+	//
+	// An example of such situation could be seen from a `VirtualScroller` debug log
+	// which was captured for a case when using `useLayoutEffect()` to update the
+	// "actual" `VirtualScroller` state after the corresponding DOM changes have been applied:
 
-	// Updates the actual `VirtualScroller` state right after a requested state update
-	// has been applied. Doesn't do anything at initial render.
-	useLayoutEffect(() => {
+	// The user has scrolled far enough: perform a re-layout
+	// ~ Update Layout (on scroll) ~
+	//
+	// Item index 2 height is required for calculations but hasn't been measured yet. Mark the item as "shown", rerender the list, measure the item's height and redo the layout.
+	//
+	// ~ Calculated Layout ~
+	// Columns count 1
+	// First shown item index 2
+	// Last shown item index 5
+	// …
+	// Item heights (231) [1056.578125, 783.125, empty × 229]
+	// Item states (231) [{…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, …]
+	//
+	// ~ Set state ~
+	// {firstShownItemIndex: 2, lastShownItemIndex: 5, …}
+	//
+	// ~ Rendered ~
+	// State {firstShownItemIndex: 2, lastShownItemIndex: 5, …}
+	//
+	// ~ Measure item heights ~
+	// Item index 2 height 719.8828125
+	// Item index 3 height 961.640625
+	// Item index 4 height 677.6640625
+	// Item index 5 height 1510.1953125
+	//
+	// ~ Update Layout (on non-measured item heights have been measured) ~
+	//
+	// ~ Calculated Layout ~
+	// Columns count 1
+	// First shown item index 4
+	// Last shown item index 5
+	// …
+	// Item heights (231) [1056.578125, 783.125, 719.8828125, 961.640625, 677.6640625, 1510.1953125, empty × 225]
+	// Item states (231) [{…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, …]
+	//
+	// ~ Set state ~
+	// {firstShownItemIndex: 4, lastShownItemIndex: 5, beforeItemsHeight: 3521.2265625, afterItemsHeight: 214090.72265624942}
+	//
+	// ~ On Item Height Did Change was called ~
+	// Item index 5
+	// ~ Re-measure item height ~
+	// ERROR "onItemHeightDidChange()" has been called for item index 5 but the item is not currently rendered and can't be measured. The exact error was: Element with index 3 was not found in the list of Rendered Item Elements in the Items Container of Virtual Scroller. There're only 2 Elements there.
+	//
+	// React: ~ The requested state is about to be applied in DOM. Set it as the `VirtualScroller` state. ~
+	// {firstShownItemIndex: 4, lastShownItemIndex: 5, …}
+	//
+	// ~ Rendered ~
+
+	// "~ Rendered ~" is what gets output when `onRender()` function gets called.
+	// It means that `useLayoutEffect()` was triggered after `onItemHeightDidChange(i)`
+	// was called and after the "ERROR" happened.
+	//
+	// The "ERROR" happened because new item indexes 4…5 were actually rendered instead of
+	// item indexes 2…5 by the time the application called `onItemHeightDidChange(i)` function
+	// inside `itemComponent`'s `useLayoutEffect()`.
+	// Item indexes 4…5 is what was requested in a `setState()` call, which called `_setNewState()`.
+	// This means that `_newState` changes have been applied to the DOM
+	// but `useLayoutEffect()` wasn't triggered immediately after that.
+	// Instead, it was triggered a right after the `itemComponent`'s `useLayoutEffect()`
+	// because child effects run before parent effects.
+	// So, the `itemComponent`'s `onHeightDidChange()` function call caught the
+	// `VirtualScroller` in an inconsistent state.
+	//
+	// To fix that, `useLayoutEffect()` gets replaced with `useInsertionEffect()`:
+	// https://blog.saeloun.com/2022/06/02/react-18-useinsertioneffect
+	// https://beta.reactjs.org/reference/react/useInsertionEffect
+	//
+	// After replacing `useLayoutEffect()` with `useInsertionEffect()`,
+	// the log shows that there's no more error:
+	//
+	// ~ Set state ~
+	// {firstShownItemIndex: 0, lastShownItemIndex: 2, …}
+	//
+	// React: ~ The requested state is about to be applied in DOM. Set it as the `VirtualScroller` state. ~
+	// {firstShownItemIndex: 0, lastShownItemIndex: 2, …}
+	//
+	// ~ On Item Height Did Change was called ~
+	// Item index 0
+	// ~ Re-measure item height ~
+	// Previous height 917
+	// New height 1064.453125
+	// ~ Item height has changed ~
+	//
+	// An alternative solution would be demanding the `itemComponent` to
+	// accept a `ref` and then measuring the corresponding DOM element height
+	// directly using the `ref`-ed DOM element rather than searching for that
+	// DOM element in the `ItemsContainer`.
+	// So if `useInsertionEffect()` gets removed from React in some hypothetical future,
+	// it could be replaced with using `ref`s on `ItemComponent`s to measure the DOM element heights.
+	//
+	useInsertionEffect(() => {
+		// Update the actual `VirtualScroller` state right before the DOM changes
+		// are going to be applied for the requested state update.
+		//
+		// This hook will run right before `useLayoutEffect()`.
+		//
+		// It doesn't make any difference which one of the two hooks to use to update
+		// the actual `VirtualScroller` state in this scenario because the two hooks
+		// run synchronously one right after another (insertion effect → DOM update → layout effect)
+		// without any free space for any `VirtualScroller` code (like the scroll event handler)
+		// to squeeze in and run in-between them, so the `VirtualScroller`'s `state`
+		// is always gonna stay consistent with what's currently rendered on screen
+		// from the `VirtualScroler`'s point of view, and the short transition period
+		// it simply doesn't see because it doesn't "wake up" during that period.
+		//
+		// Updating the actual `VirtualScroller` state right before `useLayoutEffect()`
+		// fixes the bug when an `itemComponent` calls `onHeightDidChange()` in its own
+		// `useLayoutEffect()` which would run before this `useLayoutEffect()`
+		// because children's effects run before parent's.
+		//
+		// This hook doesn't do anything at the initial render.
+		//
+		if (isDebug()) {
+			log('React: ~ The requested state is about to be applied in DOM. Set it as the `VirtualScroller` state. ~')
+			log(getStateSnapshot(_newState))
+		}
 		setState(_newState)
-	}, [
-		_newState
-	])
+	}, [_newState])
 
-	// Calls `onRender()` right after every state update (which is a re-render),
-	// and also right after the initial render.
 	useLayoutEffect(() => {
+		// Call `onRender()` right after a requested state update has been applied,
+		// and also right after the initial render.
 		onRender()
-	}, [
-		_newState,
-		// When using `USE_ITEMS_UPDATE_NO_SECOND_RENDER_OPTIMIZATION` feature,
-		// there won't be a `_setNewState()` function call when `items` property changes,
-		// hence the additional `itemsProperty` dependency.
-		USE_ITEMS_UPDATE_NO_SECOND_RENDER_OPTIMIZATION ? itemsProperty : undefined
-	])
+	}, [_newState])
 
 	return {
-		getState: () => state.current,
+		// This is the state the component should render.
+		stateToRender: _newState,
 
-		getNextState: () => nextState.current,
+		// Returns the current state of the `VirtualScroller`.
+		// This function is used in the `VirtualScroller` itself
+		// because the `state` is managed outside of it.
+		getState,
 
 		// Requests a state update.
-		//
-		// State updates are incremental meaning that this function mimicks
-		// the classic `React.Component`'s `this.setState()` behavior
-		// when calling `this.setState()` didn't replace `state` but rather merged
-		// the updated state properties over the "old" state properties.
-		//
-		// The reason for using pending state updates accumulation is that
-		// `useState()` updates are "asynchronous" (not immediate),
-		// and simply merging over `...state` would merge over potentially stale
-		// property values in cases when more than a single `updateState()` call is made
-		// before the state actually updates, resulting in losing some of those state updates.
-		//
-		// Example: the first `updateState()` call updates shown item indexes,
-		// and the second `updateState()` call updates `verticalSpacing`.
-		// If it was simply `updateState({ ...state, ...stateUpdate })`
-		// then the second state update could overwrite the first state update,
-		// resulting in incorrect items being shown/hidden.
-		//
-		updateState: (stateUpdate) => {
-			nextState.current = {
-				...nextState.current,
-				...stateUpdate
-			}
-			// If `items` property did change, the component detects it at render time
-			// and updates `VirtualScroller` items immediately by calling `.setItems()`,
-			// which, in turn, immediately calls this `updateState()` function
-			// with a `stateUpdate` argument that contains the new `items`,
-			// so checking for `stateUpdate.items` could detect situations like that.
-			//
-			// When the initial `VirtualScroller` state is being set, it contains the `.items`
-			// property too, but that initial setting is done using another function called
-			// `setInitialState()`, so using `if (stateUpdate.items)` condition here for describing
-			// just the case when `state` has been updated as a result of a `setItems()` call
-			// seems to be fine.
-			//
-			const _newState = nextState.current
-			if (stateUpdate.items && USE_ITEMS_UPDATE_NO_SECOND_RENDER_OPTIMIZATION) {
-				setState(_newState)
-			} else {
-				_setNewState(_newState)
-			}
-		}
+		setState: _setNewState
 	}
 }

package/source/react/useStyle.js

@@ -2,7 +2,7 @@ import px from '../utility/px.js'
 
 export default function useStyle({
 	tbody,
-	getNextState
+	state
 }) {
 	if (tbody) {
 		return
@@ -11,7 +11,7 @@ export default function useStyle({
 	const {
 		beforeItemsHeight,
 		afterItemsHeight
-	} = getNextState()
+	} = state
 
 	return {
 		paddingTop: px(beforeItemsHeight),

package/source/react/{useHandleItemIndexesChange.js → useUpdateItemKeysOnItemsChange.js}

@@ -1,4 +1,6 @@
-import { useRef } from 'react'
+import log from '../utility/debug.js'
+
+import useOnChange from './useOnChange.js'
 
 // If the order of the `items` changes, or new `items` get prepended resulting in a "shift":
 //
@@ -9,20 +11,23 @@ import { useRef } from 'react'
 //   might result in bugs, which React would do with its "re-using" policy
 //   if the unique `key` workaround hasn't been used.
 //
-export default function useHandleItemIndexesChange({
+export default function useUpdateItemKeysOnItemsChange(itemsBeingRendered, {
 	virtualScroller,
-	itemsBeingRendered,
+	usesAutogeneratedItemKeys,
 	updateItemKeysForNewItems
 }) {
-	const previousItemsBeingRenderedRef = useRef(itemsBeingRendered)
-	const previousItemsBeingRendered = previousItemsBeingRenderedRef.current
-	const haveItemsChanged = itemsBeingRendered !== previousItemsBeingRendered
-	previousItemsBeingRenderedRef.current = itemsBeingRendered
+	// Update item keys if the items being rendered have changed.
+	useOnChange(itemsBeingRendered, (itemsBeingRendered, previousItemsBeingRendered) => {
+		if (!usesAutogeneratedItemKeys) {
+			return
+		}
+
+		log('React: ~ Different `items` are about to be rendered', itemsBeingRendered)
 
-	if (haveItemsChanged) {
 		let shouldUpdateItemKeys = true
 
 		const itemsDiff = virtualScroller.getItemsDiff(previousItemsBeingRendered, itemsBeingRendered)
+
 		// `itemsDiff` will be `undefined` in case of a non-incremental items list change.
 		if (itemsDiff) {
 			const {
@@ -30,11 +35,13 @@ export default function useHandleItemIndexesChange({
 				appendedItemsCount
 			} = itemsDiff
 			if (prependedItemsCount === 0 && appendedItemsCount === 0) {
+				log('React: ~ The `items` elements to be rendered are identical to the previously rendered ones')
 				// The items order hasn't changed.
 				// No need to re-generate the `key` prefix.
 				shouldUpdateItemKeys = false
 			}
 			else if (prependedItemsCount === 0 && appendedItemsCount > 0) {
+				log('React: ~ The `items` elements order hasn\'t changed:', appendedItemsCount, 'items have been appended')
 				// The item order hasn't changed.
 				// No need to re-generate the `key` prefix.
 				shouldUpdateItemKeys = false
@@ -43,7 +50,8 @@ export default function useHandleItemIndexesChange({
 
 		// Update React element `key`s for the new set of `items`.
 		if (shouldUpdateItemKeys) {
+			log('React: ~ Update item `key`s')
 			updateItemKeysForNewItems()
 		}
-	}
+	})
 }

package/source/test/ItemsContainer.js

@@ -1,3 +1,5 @@
+import ItemNotRenderedError from '../ItemNotRenderedError.js'
+
 export default class ItemsContainer {
 	/**
 	 * Constructs a new "container" from an element.
@@ -16,9 +18,18 @@ export default class ItemsContainer {
 		const children = this.getElement().children
 		const maxWidth = this.getElement().width
 		let topOffset = this.getElement().paddingTop
+
 		let rowWidth
 		let rowHeight
 		let startNewRow = true
+
+		if (renderedElementIndex > children.length - 1) {
+			throw new ItemNotRenderedError({
+				renderedElementIndex,
+				renderedElementsCount: children.length
+			})
+		}
+
 		let i = 0
 		while (i <= renderedElementIndex) {
 			if (startNewRow || rowWidth + children[i].width > maxWidth) {
@@ -39,6 +50,7 @@ export default class ItemsContainer {
 			}
 			i++
 		}
+
 		return topOffset
 	}
 
@@ -48,7 +60,16 @@ export default class ItemsContainer {
 	 * @return {number}
 	 */
 	getNthRenderedItemHeight(renderedElementIndex) {
-		return this.getElement().children[renderedElementIndex].height
+		const children = this.getElement().children
+
+		if (renderedElementIndex > children.length - 1) {
+			throw new ItemNotRenderedError({
+				renderedElementIndex,
+				renderedElementsCount: children.length
+			})
+		}
+
+		return children[renderedElementIndex].height
 	}
 
 	/**

package/source/utility/debug.js

@@ -13,12 +13,17 @@ export function warn(...args) {
 	}
 }
 
+function error(...args) {
+	console.error(...['[virtual-scroller]'].concat(args))
+}
+
 export function reportError(...args) {
+	const createError = () => new Error(['[virtual-scroller]'].concat(args).join(' '))
 	if (typeof window !== 'undefined') {
 		// In a web browser.
 		// Output a debug message immediately so that it's known
 		// at which point did the error occur between other debug logs.
-		log.apply(this, ['ERROR'].concat(args))
+		error.apply(this, ['ERROR'].concat(args))
 		setTimeout(() => {
 			// Throw an error in a timeout so that it doesn't interrupt the application's flow.
 			// At the same time, by throwing a client-side error, such error could be spotted
@@ -26,11 +31,20 @@ export function reportError(...args) {
 			// in the console.
 			// The `.join(' ')` part doesn't support stringifying JSON objects,
 			// but those don't seem to be used in any of the error messages.
-			throw new Error(['[virtual-scroller]'].concat(args).join(' '))
+			throw createError()
 		}, 0)
 	} else {
-		// On a server.
-		console.error(...['[virtual-scroller]'].concat(args))
+		// In Node.js.
+		// If tests are being run, throw in case of any errors.
+		const catchError = getGlobalVariable('VirtualScrollerCatchError')
+		if (catchError) {
+			return catchError(createError())
+		}
+		if (getGlobalVariable('VirtualScrollerThrowErrors')) {
+			throw createError()
+		}
+		// Print the error in the console.
+		error.apply(this, ['ERROR'].concat(args))
 	}
 }
 

package/commonjs/react/useHandleItemIndexesChange.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"useHandleItemIndexesChange.js","names":["useHandleItemIndexesChange","virtualScroller","itemsBeingRendered","updateItemKeysForNewItems","previousItemsBeingRenderedRef","useRef","previousItemsBeingRendered","current","haveItemsChanged","shouldUpdateItemKeys","itemsDiff","getItemsDiff","prependedItemsCount","appendedItemsCount"],"sources":["../../source/react/useHandleItemIndexesChange.js"],"sourcesContent":["import { useRef } from 'react'\r\n\r\n// If the order of the `items` changes, or new `items` get prepended resulting in a \"shift\":\r\n//\r\n// * Re-generate the React `key` prefix for item elements\r\n//   so that all item components are re-rendered for the new `items` list.\r\n//   That's because item components may have their own internal state,\r\n//   and simply passing another `item` property for an item component\r\n//   might result in bugs, which React would do with its \"re-using\" policy\r\n//   if the unique `key` workaround hasn't been used.\r\n//\r\nexport default function useHandleItemIndexesChange({\r\n\tvirtualScroller,\r\n\titemsBeingRendered,\r\n\tupdateItemKeysForNewItems\r\n}) {\r\n\tconst previousItemsBeingRenderedRef = useRef(itemsBeingRendered)\r\n\tconst previousItemsBeingRendered = previousItemsBeingRenderedRef.current\r\n\tconst haveItemsChanged = itemsBeingRendered !== previousItemsBeingRendered\r\n\tpreviousItemsBeingRenderedRef.current = itemsBeingRendered\r\n\r\n\tif (haveItemsChanged) {\r\n\t\tlet shouldUpdateItemKeys = true\r\n\r\n\t\tconst itemsDiff = virtualScroller.getItemsDiff(previousItemsBeingRendered, itemsBeingRendered)\r\n\t\t// `itemsDiff` will be `undefined` in case of a non-incremental items list change.\r\n\t\tif (itemsDiff) {\r\n\t\t\tconst {\r\n\t\t\t\tprependedItemsCount,\r\n\t\t\t\tappendedItemsCount\r\n\t\t\t} = itemsDiff\r\n\t\t\tif (prependedItemsCount === 0 && appendedItemsCount === 0) {\r\n\t\t\t\t// The items order hasn't changed.\r\n\t\t\t\t// No need to re-generate the `key` prefix.\r\n\t\t\t\tshouldUpdateItemKeys = false\r\n\t\t\t}\r\n\t\t\telse if (prependedItemsCount === 0 && appendedItemsCount > 0) {\r\n\t\t\t\t// The item order hasn't changed.\r\n\t\t\t\t// No need to re-generate the `key` prefix.\r\n\t\t\t\tshouldUpdateItemKeys = false\r\n\t\t\t}\r\n\t\t}\r\n\r\n\t\t// Update React element `key`s for the new set of `items`.\r\n\t\tif (shouldUpdateItemKeys) {\r\n\t\t\tupdateItemKeysForNewItems()\r\n\t\t}\r\n\t}\r\n}"],"mappings":";;;;;;;AAAA;;AAEA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACe,SAASA,0BAAT,OAIZ;EAAA,IAHFC,eAGE,QAHFA,eAGE;EAAA,IAFFC,kBAEE,QAFFA,kBAEE;EAAA,IADFC,yBACE,QADFA,yBACE;EACF,IAAMC,6BAA6B,GAAG,IAAAC,aAAA,EAAOH,kBAAP,CAAtC;EACA,IAAMI,0BAA0B,GAAGF,6BAA6B,CAACG,OAAjE;EACA,IAAMC,gBAAgB,GAAGN,kBAAkB,KAAKI,0BAAhD;EACAF,6BAA6B,CAACG,OAA9B,GAAwCL,kBAAxC;;EAEA,IAAIM,gBAAJ,EAAsB;IACrB,IAAIC,oBAAoB,GAAG,IAA3B;IAEA,IAAMC,SAAS,GAAGT,eAAe,CAACU,YAAhB,CAA6BL,0BAA7B,EAAyDJ,kBAAzD,CAAlB,CAHqB,CAIrB;;IACA,IAAIQ,SAAJ,EAAe;MACd,IACCE,mBADD,GAGIF,SAHJ,CACCE,mBADD;MAAA,IAECC,kBAFD,GAGIH,SAHJ,CAECG,kBAFD;;MAIA,IAAID,mBAAmB,KAAK,CAAxB,IAA6BC,kBAAkB,KAAK,CAAxD,EAA2D;QAC1D;QACA;QACAJ,oBAAoB,GAAG,KAAvB;MACA,CAJD,MAKK,IAAIG,mBAAmB,KAAK,CAAxB,IAA6BC,kBAAkB,GAAG,CAAtD,EAAyD;QAC7D;QACA;QACAJ,oBAAoB,GAAG,KAAvB;MACA;IACD,CApBoB,CAsBrB;;;IACA,IAAIA,oBAAJ,EAA0B;MACzBN,yBAAyB;IACzB;EACD;AACD"}

package/commonjs/react/useHandleItemsPropertyChange.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"useHandleItemsPropertyChange.js","names":["useHandleItemsPropertyChange","itemsProperty","virtualScroller","preserveScrollPosition","preserveScrollPositionOnPrependItems","nextItems","previousItemsProperty","useRef","hasItemsPropertyChanged","current","shouldUpdateItems","itemsDiff","getItemsDiff","prependedItemsCount","appendedItemsCount","setItems"],"sources":["../../source/react/useHandleItemsPropertyChange.js"],"sourcesContent":["import { useRef } from 'react'\r\n\r\n// If new `items` property is passed:\r\n//\r\n// * Store the scroll Y position for the first one of the current items\r\n//   so that it could potentially (in some cases) be restored after the\r\n//   new `items` are rendered.\r\n//\r\n// * Call `VirtualScroller.setItems()` function.\r\n//\r\nexport default function useHandleItemsPropertyChange(itemsProperty, {\r\n\tvirtualScroller,\r\n\t// `preserveScrollPosition` property name is deprecated,\r\n\t// use `preserveScrollPositionOnPrependItems` property instead.\r\n\tpreserveScrollPosition,\r\n\tpreserveScrollPositionOnPrependItems,\r\n\tnextItems\r\n}) {\r\n\t// During render, check if the `items` list has changed.\r\n\t// If it has, capture the Y scroll position and updated item element `key`s.\r\n\r\n\t// A long \"advanced\" sidenote on why capturing scroll Y position\r\n\t// is done during render instead of in an \"effect\":\r\n\t//\r\n\t// Previously, capturing scroll Y position was being done in `useLayoutEffect()`\r\n\t// but it was later found out that it wouldn't work for a \"Show previous\" button\r\n\t// scenario because that button would get hidden by the time `useLayoutEffect()`\r\n\t// gets called when there're no more \"previous\" items to show.\r\n\t//\r\n\t// Consider this code example:\r\n\t//\r\n\t// const { fromIndex, items } = this.state\r\n\t// const items = allItems.slice(fromIndex)\r\n\t// return (\r\n\t// \t{fromIndex > 0 &&\r\n\t// \t\t<button onClick={this.onShowPrevious}>\r\n\t// \t\t\tShow previous\r\n\t// \t\t</button>\r\n\t// \t}\r\n\t// \t<VirtualScroller\r\n\t// \t\titems={items}\r\n\t// \t\titemComponent={ItemComponent}/>\r\n\t// )\r\n\t//\r\n\t// Consider a user clicks \"Show previous\" to show the items from the start.\r\n\t// By the time `componentDidUpdate()` is called on `<VirtualScroller/>`,\r\n\t// the \"Show previous\" button has already been hidden\r\n\t// (because there're no more \"previous\" items)\r\n\t// which results in the scroll Y position jumping forward\r\n\t// by the height of that \"Show previous\" button.\r\n\t// This is because `<VirtualScroller/>` captures scroll Y\r\n\t// position when items are prepended via `.setItems()`\r\n\t// when the \"Show previous\" button is still being shown,\r\n\t// and then restores scroll Y position in `.onRender()`\r\n\t// when the \"Show previous\" button has already been hidden:\r\n\t// that's the reason for the scroll Y \"jump\".\r\n\t//\r\n\t// To prevent that, scroll Y position is captured at `render()`\r\n\t// time rather than later in `componentDidUpdate()`: this way,\r\n\t// scroll Y position is captured while the \"Show previous\" button\r\n\t// is still being shown.\r\n\r\n\tconst previousItemsProperty = useRef(itemsProperty)\r\n\tconst hasItemsPropertyChanged = itemsProperty !== previousItemsProperty.current\r\n\tpreviousItemsProperty.current = itemsProperty\r\n\r\n\tif (hasItemsPropertyChanged) {\r\n\t\tlet shouldUpdateItems = true\r\n\r\n\t\t// Analyze the upcoming `items` change.\r\n\t\tconst itemsDiff = virtualScroller.getItemsDiff(nextItems, itemsProperty)\r\n\r\n\t\t// `itemsDiff` will be `undefined` in case of a non-incremental items list change.\r\n\t\tif (itemsDiff) {\r\n\t\t\tconst {\r\n\t\t\t\tprependedItemsCount,\r\n\t\t\t\tappendedItemsCount\r\n\t\t\t} = itemsDiff\r\n\t\t\tif (prependedItemsCount === 0 && appendedItemsCount === 0) {\r\n\t\t\t\t// The items order hasn't changed.\r\n\t\t\t\t// No need to update them in `VirtualScroller` or to snapshot the Y scroll position.\r\n\t\t\t\tshouldUpdateItems = false\r\n\t\t\t}\r\n\t\t}\r\n\r\n\t\tif (shouldUpdateItems) {\r\n\t\t\t// Request to update the `items` in `VirtualScroller`.\r\n\t\t\t// This will result in a `setState()` call.\r\n\t\t\t// The new items won't be rendered until that state update is applied.\r\n\t\t\tvirtualScroller.setItems(itemsProperty, {\r\n\t\t\t\t// `preserveScrollPosition` property name is deprecated,\r\n\t\t\t\t// use `preserveScrollPositionOnPrependItems` property instead.\r\n\t\t\t\tpreserveScrollPositionOnPrependItems: preserveScrollPositionOnPrependItems || preserveScrollPosition\r\n\t\t\t})\r\n\t\t}\r\n\t}\r\n}"],"mappings":";;;;;;;AAAA;;AAEA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACe,SAASA,4BAAT,CAAsCC,aAAtC,QAOZ;EAAA,IANFC,eAME,QANFA,eAME;EAAA,IAHFC,sBAGE,QAHFA,sBAGE;EAAA,IAFFC,oCAEE,QAFFA,oCAEE;EAAA,IADFC,SACE,QADFA,SACE;EACF;EACA;EAEA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EAEA,IAAMC,qBAAqB,GAAG,IAAAC,aAAA,EAAON,aAAP,CAA9B;EACA,IAAMO,uBAAuB,GAAGP,aAAa,KAAKK,qBAAqB,CAACG,OAAxE;EACAH,qBAAqB,CAACG,OAAtB,GAAgCR,aAAhC;;EAEA,IAAIO,uBAAJ,EAA6B;IAC5B,IAAIE,iBAAiB,GAAG,IAAxB,CAD4B,CAG5B;;IACA,IAAMC,SAAS,GAAGT,eAAe,CAACU,YAAhB,CAA6BP,SAA7B,EAAwCJ,aAAxC,CAAlB,CAJ4B,CAM5B;;IACA,IAAIU,SAAJ,EAAe;MACd,IACCE,mBADD,GAGIF,SAHJ,CACCE,mBADD;MAAA,IAECC,kBAFD,GAGIH,SAHJ,CAECG,kBAFD;;MAIA,IAAID,mBAAmB,KAAK,CAAxB,IAA6BC,kBAAkB,KAAK,CAAxD,EAA2D;QAC1D;QACA;QACAJ,iBAAiB,GAAG,KAApB;MACA;IACD;;IAED,IAAIA,iBAAJ,EAAuB;MACtB;MACA;MACA;MACAR,eAAe,CAACa,QAAhB,CAAyBd,aAAzB,EAAwC;QACvC;QACA;QACAG,oCAAoC,EAAEA,oCAAoC,IAAID;MAHvC,CAAxC;IAKA;EACD;AACD"}

package/commonjs/react/useOnItemHeightChange.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"useOnItemHeightChange.js","names":["useOnItemHeightChange","initialItemsCount","virtualScroller","initialCacheValue","useMemo","Array","cache","useRef","getOnItemHeightChange","useCallback","i","current","onItemHeightChange"],"sources":["../../source/react/useOnItemHeightChange.js"],"sourcesContent":["import { useMemo, useRef, useCallback } from 'react'\r\n\r\nexport default function useOnItemHeightChange({\r\n\tinitialItemsCount,\r\n\tvirtualScroller\r\n}) {\r\n\t// Only compute the initial cache value once.\r\n\tconst initialCacheValue = useMemo(() => {\r\n\t\treturn new Array(initialItemsCount)\r\n\t}, [])\r\n\r\n\t// Handler functions cache.\r\n\tconst cache = useRef(initialCacheValue)\r\n\r\n\t// Caches per-item `onItemHeightChange` functions' \"references\"\r\n\t// so that item components don't get re-rendered needlessly.\r\n\tconst getOnItemHeightChange = useCallback((i) => {\r\n\t\tif (!cache.current[i]) {\r\n\t\t\tcache.current[i] = () => virtualScroller.onItemHeightChange(i)\r\n\t\t}\r\n\t\treturn cache.current[i]\r\n\t}, [\r\n\t\tvirtualScroller,\r\n\t\tcache\r\n\t])\r\n\r\n\treturn getOnItemHeightChange\r\n}"],"mappings":";;;;;;;AAAA;;AAEe,SAASA,qBAAT,OAGZ;EAAA,IAFFC,iBAEE,QAFFA,iBAEE;EAAA,IADFC,eACE,QADFA,eACE;EACF;EACA,IAAMC,iBAAiB,GAAG,IAAAC,cAAA,EAAQ,YAAM;IACvC,OAAO,IAAIC,KAAJ,CAAUJ,iBAAV,CAAP;EACA,CAFyB,EAEvB,EAFuB,CAA1B,CAFE,CAMF;;EACA,IAAMK,KAAK,GAAG,IAAAC,aAAA,EAAOJ,iBAAP,CAAd,CAPE,CASF;EACA;;EACA,IAAMK,qBAAqB,GAAG,IAAAC,kBAAA,EAAY,UAACC,CAAD,EAAO;IAChD,IAAI,CAACJ,KAAK,CAACK,OAAN,CAAcD,CAAd,CAAL,EAAuB;MACtBJ,KAAK,CAACK,OAAN,CAAcD,CAAd,IAAmB;QAAA,OAAMR,eAAe,CAACU,kBAAhB,CAAmCF,CAAnC,CAAN;MAAA,CAAnB;IACA;;IACD,OAAOJ,KAAK,CAACK,OAAN,CAAcD,CAAd,CAAP;EACA,CAL6B,EAK3B,CACFR,eADE,EAEFI,KAFE,CAL2B,CAA9B;EAUA,OAAOE,qBAAP;AACA"}

package/modules/react/useHandleItemIndexesChange.js

@@ -1,45 +0,0 @@
-import { useRef } from 'react'; // If the order of the `items` changes, or new `items` get prepended resulting in a "shift":
-//
-// * Re-generate the React `key` prefix for item elements
-//   so that all item components are re-rendered for the new `items` list.
-//   That's because item components may have their own internal state,
-//   and simply passing another `item` property for an item component
-//   might result in bugs, which React would do with its "re-using" policy
-//   if the unique `key` workaround hasn't been used.
-//
-
-export default function useHandleItemIndexesChange(_ref) {
-  var virtualScroller = _ref.virtualScroller,
-      itemsBeingRendered = _ref.itemsBeingRendered,
-      updateItemKeysForNewItems = _ref.updateItemKeysForNewItems;
-  var previousItemsBeingRenderedRef = useRef(itemsBeingRendered);
-  var previousItemsBeingRendered = previousItemsBeingRenderedRef.current;
-  var haveItemsChanged = itemsBeingRendered !== previousItemsBeingRendered;
-  previousItemsBeingRenderedRef.current = itemsBeingRendered;
-
-  if (haveItemsChanged) {
-    var shouldUpdateItemKeys = true;
-    var itemsDiff = virtualScroller.getItemsDiff(previousItemsBeingRendered, itemsBeingRendered); // `itemsDiff` will be `undefined` in case of a non-incremental items list change.
-
-    if (itemsDiff) {
-      var prependedItemsCount = itemsDiff.prependedItemsCount,
-          appendedItemsCount = itemsDiff.appendedItemsCount;
-
-      if (prependedItemsCount === 0 && appendedItemsCount === 0) {
-        // The items order hasn't changed.
-        // No need to re-generate the `key` prefix.
-        shouldUpdateItemKeys = false;
-      } else if (prependedItemsCount === 0 && appendedItemsCount > 0) {
-        // The item order hasn't changed.
-        // No need to re-generate the `key` prefix.
-        shouldUpdateItemKeys = false;
-      }
-    } // Update React element `key`s for the new set of `items`.
-
-
-    if (shouldUpdateItemKeys) {
-      updateItemKeysForNewItems();
-    }
-  }
-}
-//# sourceMappingURL=useHandleItemIndexesChange.js.map

package/modules/react/useHandleItemIndexesChange.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"useHandleItemIndexesChange.js","names":["useRef","useHandleItemIndexesChange","virtualScroller","itemsBeingRendered","updateItemKeysForNewItems","previousItemsBeingRenderedRef","previousItemsBeingRendered","current","haveItemsChanged","shouldUpdateItemKeys","itemsDiff","getItemsDiff","prependedItemsCount","appendedItemsCount"],"sources":["../../source/react/useHandleItemIndexesChange.js"],"sourcesContent":["import { useRef } from 'react'\r\n\r\n// If the order of the `items` changes, or new `items` get prepended resulting in a \"shift\":\r\n//\r\n// * Re-generate the React `key` prefix for item elements\r\n//   so that all item components are re-rendered for the new `items` list.\r\n//   That's because item components may have their own internal state,\r\n//   and simply passing another `item` property for an item component\r\n//   might result in bugs, which React would do with its \"re-using\" policy\r\n//   if the unique `key` workaround hasn't been used.\r\n//\r\nexport default function useHandleItemIndexesChange({\r\n\tvirtualScroller,\r\n\titemsBeingRendered,\r\n\tupdateItemKeysForNewItems\r\n}) {\r\n\tconst previousItemsBeingRenderedRef = useRef(itemsBeingRendered)\r\n\tconst previousItemsBeingRendered = previousItemsBeingRenderedRef.current\r\n\tconst haveItemsChanged = itemsBeingRendered !== previousItemsBeingRendered\r\n\tpreviousItemsBeingRenderedRef.current = itemsBeingRendered\r\n\r\n\tif (haveItemsChanged) {\r\n\t\tlet shouldUpdateItemKeys = true\r\n\r\n\t\tconst itemsDiff = virtualScroller.getItemsDiff(previousItemsBeingRendered, itemsBeingRendered)\r\n\t\t// `itemsDiff` will be `undefined` in case of a non-incremental items list change.\r\n\t\tif (itemsDiff) {\r\n\t\t\tconst {\r\n\t\t\t\tprependedItemsCount,\r\n\t\t\t\tappendedItemsCount\r\n\t\t\t} = itemsDiff\r\n\t\t\tif (prependedItemsCount === 0 && appendedItemsCount === 0) {\r\n\t\t\t\t// The items order hasn't changed.\r\n\t\t\t\t// No need to re-generate the `key` prefix.\r\n\t\t\t\tshouldUpdateItemKeys = false\r\n\t\t\t}\r\n\t\t\telse if (prependedItemsCount === 0 && appendedItemsCount > 0) {\r\n\t\t\t\t// The item order hasn't changed.\r\n\t\t\t\t// No need to re-generate the `key` prefix.\r\n\t\t\t\tshouldUpdateItemKeys = false\r\n\t\t\t}\r\n\t\t}\r\n\r\n\t\t// Update React element `key`s for the new set of `items`.\r\n\t\tif (shouldUpdateItemKeys) {\r\n\t\t\tupdateItemKeysForNewItems()\r\n\t\t}\r\n\t}\r\n}"],"mappings":"AAAA,SAASA,MAAT,QAAuB,OAAvB,C,CAEA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;;AACA,eAAe,SAASC,0BAAT,OAIZ;EAAA,IAHFC,eAGE,QAHFA,eAGE;EAAA,IAFFC,kBAEE,QAFFA,kBAEE;EAAA,IADFC,yBACE,QADFA,yBACE;EACF,IAAMC,6BAA6B,GAAGL,MAAM,CAACG,kBAAD,CAA5C;EACA,IAAMG,0BAA0B,GAAGD,6BAA6B,CAACE,OAAjE;EACA,IAAMC,gBAAgB,GAAGL,kBAAkB,KAAKG,0BAAhD;EACAD,6BAA6B,CAACE,OAA9B,GAAwCJ,kBAAxC;;EAEA,IAAIK,gBAAJ,EAAsB;IACrB,IAAIC,oBAAoB,GAAG,IAA3B;IAEA,IAAMC,SAAS,GAAGR,eAAe,CAACS,YAAhB,CAA6BL,0BAA7B,EAAyDH,kBAAzD,CAAlB,CAHqB,CAIrB;;IACA,IAAIO,SAAJ,EAAe;MACd,IACCE,mBADD,GAGIF,SAHJ,CACCE,mBADD;MAAA,IAECC,kBAFD,GAGIH,SAHJ,CAECG,kBAFD;;MAIA,IAAID,mBAAmB,KAAK,CAAxB,IAA6BC,kBAAkB,KAAK,CAAxD,EAA2D;QAC1D;QACA;QACAJ,oBAAoB,GAAG,KAAvB;MACA,CAJD,MAKK,IAAIG,mBAAmB,KAAK,CAAxB,IAA6BC,kBAAkB,GAAG,CAAtD,EAAyD;QAC7D;QACA;QACAJ,oBAAoB,GAAG,KAAvB;MACA;IACD,CApBoB,CAsBrB;;;IACA,IAAIA,oBAAJ,EAA0B;MACzBL,yBAAyB;IACzB;EACD;AACD"}

package/modules/react/useHandleItemsPropertyChange.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"useHandleItemsPropertyChange.js","names":["useRef","useHandleItemsPropertyChange","itemsProperty","virtualScroller","preserveScrollPosition","preserveScrollPositionOnPrependItems","nextItems","previousItemsProperty","hasItemsPropertyChanged","current","shouldUpdateItems","itemsDiff","getItemsDiff","prependedItemsCount","appendedItemsCount","setItems"],"sources":["../../source/react/useHandleItemsPropertyChange.js"],"sourcesContent":["import { useRef } from 'react'\r\n\r\n// If new `items` property is passed:\r\n//\r\n// * Store the scroll Y position for the first one of the current items\r\n//   so that it could potentially (in some cases) be restored after the\r\n//   new `items` are rendered.\r\n//\r\n// * Call `VirtualScroller.setItems()` function.\r\n//\r\nexport default function useHandleItemsPropertyChange(itemsProperty, {\r\n\tvirtualScroller,\r\n\t// `preserveScrollPosition` property name is deprecated,\r\n\t// use `preserveScrollPositionOnPrependItems` property instead.\r\n\tpreserveScrollPosition,\r\n\tpreserveScrollPositionOnPrependItems,\r\n\tnextItems\r\n}) {\r\n\t// During render, check if the `items` list has changed.\r\n\t// If it has, capture the Y scroll position and updated item element `key`s.\r\n\r\n\t// A long \"advanced\" sidenote on why capturing scroll Y position\r\n\t// is done during render instead of in an \"effect\":\r\n\t//\r\n\t// Previously, capturing scroll Y position was being done in `useLayoutEffect()`\r\n\t// but it was later found out that it wouldn't work for a \"Show previous\" button\r\n\t// scenario because that button would get hidden by the time `useLayoutEffect()`\r\n\t// gets called when there're no more \"previous\" items to show.\r\n\t//\r\n\t// Consider this code example:\r\n\t//\r\n\t// const { fromIndex, items } = this.state\r\n\t// const items = allItems.slice(fromIndex)\r\n\t// return (\r\n\t// \t{fromIndex > 0 &&\r\n\t// \t\t<button onClick={this.onShowPrevious}>\r\n\t// \t\t\tShow previous\r\n\t// \t\t</button>\r\n\t// \t}\r\n\t// \t<VirtualScroller\r\n\t// \t\titems={items}\r\n\t// \t\titemComponent={ItemComponent}/>\r\n\t// )\r\n\t//\r\n\t// Consider a user clicks \"Show previous\" to show the items from the start.\r\n\t// By the time `componentDidUpdate()` is called on `<VirtualScroller/>`,\r\n\t// the \"Show previous\" button has already been hidden\r\n\t// (because there're no more \"previous\" items)\r\n\t// which results in the scroll Y position jumping forward\r\n\t// by the height of that \"Show previous\" button.\r\n\t// This is because `<VirtualScroller/>` captures scroll Y\r\n\t// position when items are prepended via `.setItems()`\r\n\t// when the \"Show previous\" button is still being shown,\r\n\t// and then restores scroll Y position in `.onRender()`\r\n\t// when the \"Show previous\" button has already been hidden:\r\n\t// that's the reason for the scroll Y \"jump\".\r\n\t//\r\n\t// To prevent that, scroll Y position is captured at `render()`\r\n\t// time rather than later in `componentDidUpdate()`: this way,\r\n\t// scroll Y position is captured while the \"Show previous\" button\r\n\t// is still being shown.\r\n\r\n\tconst previousItemsProperty = useRef(itemsProperty)\r\n\tconst hasItemsPropertyChanged = itemsProperty !== previousItemsProperty.current\r\n\tpreviousItemsProperty.current = itemsProperty\r\n\r\n\tif (hasItemsPropertyChanged) {\r\n\t\tlet shouldUpdateItems = true\r\n\r\n\t\t// Analyze the upcoming `items` change.\r\n\t\tconst itemsDiff = virtualScroller.getItemsDiff(nextItems, itemsProperty)\r\n\r\n\t\t// `itemsDiff` will be `undefined` in case of a non-incremental items list change.\r\n\t\tif (itemsDiff) {\r\n\t\t\tconst {\r\n\t\t\t\tprependedItemsCount,\r\n\t\t\t\tappendedItemsCount\r\n\t\t\t} = itemsDiff\r\n\t\t\tif (prependedItemsCount === 0 && appendedItemsCount === 0) {\r\n\t\t\t\t// The items order hasn't changed.\r\n\t\t\t\t// No need to update them in `VirtualScroller` or to snapshot the Y scroll position.\r\n\t\t\t\tshouldUpdateItems = false\r\n\t\t\t}\r\n\t\t}\r\n\r\n\t\tif (shouldUpdateItems) {\r\n\t\t\t// Request to update the `items` in `VirtualScroller`.\r\n\t\t\t// This will result in a `setState()` call.\r\n\t\t\t// The new items won't be rendered until that state update is applied.\r\n\t\t\tvirtualScroller.setItems(itemsProperty, {\r\n\t\t\t\t// `preserveScrollPosition` property name is deprecated,\r\n\t\t\t\t// use `preserveScrollPositionOnPrependItems` property instead.\r\n\t\t\t\tpreserveScrollPositionOnPrependItems: preserveScrollPositionOnPrependItems || preserveScrollPosition\r\n\t\t\t})\r\n\t\t}\r\n\t}\r\n}"],"mappings":"AAAA,SAASA,MAAT,QAAuB,OAAvB,C,CAEA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;;AACA,eAAe,SAASC,4BAAT,CAAsCC,aAAtC,QAOZ;EAAA,IANFC,eAME,QANFA,eAME;EAAA,IAHFC,sBAGE,QAHFA,sBAGE;EAAA,IAFFC,oCAEE,QAFFA,oCAEE;EAAA,IADFC,SACE,QADFA,SACE;EACF;EACA;EAEA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EACA;EAEA,IAAMC,qBAAqB,GAAGP,MAAM,CAACE,aAAD,CAApC;EACA,IAAMM,uBAAuB,GAAGN,aAAa,KAAKK,qBAAqB,CAACE,OAAxE;EACAF,qBAAqB,CAACE,OAAtB,GAAgCP,aAAhC;;EAEA,IAAIM,uBAAJ,EAA6B;IAC5B,IAAIE,iBAAiB,GAAG,IAAxB,CAD4B,CAG5B;;IACA,IAAMC,SAAS,GAAGR,eAAe,CAACS,YAAhB,CAA6BN,SAA7B,EAAwCJ,aAAxC,CAAlB,CAJ4B,CAM5B;;IACA,IAAIS,SAAJ,EAAe;MACd,IACCE,mBADD,GAGIF,SAHJ,CACCE,mBADD;MAAA,IAECC,kBAFD,GAGIH,SAHJ,CAECG,kBAFD;;MAIA,IAAID,mBAAmB,KAAK,CAAxB,IAA6BC,kBAAkB,KAAK,CAAxD,EAA2D;QAC1D;QACA;QACAJ,iBAAiB,GAAG,KAApB;MACA;IACD;;IAED,IAAIA,iBAAJ,EAAuB;MACtB;MACA;MACA;MACAP,eAAe,CAACY,QAAhB,CAAyBb,aAAzB,EAAwC;QACvC;QACA;QACAG,oCAAoC,EAAEA,oCAAoC,IAAID;MAHvC,CAAxC;IAKA;EACD;AACD"}

package/modules/react/useOnItemHeightChange.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"useOnItemHeightChange.js","names":["useMemo","useRef","useCallback","useOnItemHeightChange","initialItemsCount","virtualScroller","initialCacheValue","Array","cache","getOnItemHeightChange","i","current","onItemHeightChange"],"sources":["../../source/react/useOnItemHeightChange.js"],"sourcesContent":["import { useMemo, useRef, useCallback } from 'react'\r\n\r\nexport default function useOnItemHeightChange({\r\n\tinitialItemsCount,\r\n\tvirtualScroller\r\n}) {\r\n\t// Only compute the initial cache value once.\r\n\tconst initialCacheValue = useMemo(() => {\r\n\t\treturn new Array(initialItemsCount)\r\n\t}, [])\r\n\r\n\t// Handler functions cache.\r\n\tconst cache = useRef(initialCacheValue)\r\n\r\n\t// Caches per-item `onItemHeightChange` functions' \"references\"\r\n\t// so that item components don't get re-rendered needlessly.\r\n\tconst getOnItemHeightChange = useCallback((i) => {\r\n\t\tif (!cache.current[i]) {\r\n\t\t\tcache.current[i] = () => virtualScroller.onItemHeightChange(i)\r\n\t\t}\r\n\t\treturn cache.current[i]\r\n\t}, [\r\n\t\tvirtualScroller,\r\n\t\tcache\r\n\t])\r\n\r\n\treturn getOnItemHeightChange\r\n}"],"mappings":"AAAA,SAASA,OAAT,EAAkBC,MAAlB,EAA0BC,WAA1B,QAA6C,OAA7C;AAEA,eAAe,SAASC,qBAAT,OAGZ;EAAA,IAFFC,iBAEE,QAFFA,iBAEE;EAAA,IADFC,eACE,QADFA,eACE;EACF;EACA,IAAMC,iBAAiB,GAAGN,OAAO,CAAC,YAAM;IACvC,OAAO,IAAIO,KAAJ,CAAUH,iBAAV,CAAP;EACA,CAFgC,EAE9B,EAF8B,CAAjC,CAFE,CAMF;;EACA,IAAMI,KAAK,GAAGP,MAAM,CAACK,iBAAD,CAApB,CAPE,CASF;EACA;;EACA,IAAMG,qBAAqB,GAAGP,WAAW,CAAC,UAACQ,CAAD,EAAO;IAChD,IAAI,CAACF,KAAK,CAACG,OAAN,CAAcD,CAAd,CAAL,EAAuB;MACtBF,KAAK,CAACG,OAAN,CAAcD,CAAd,IAAmB;QAAA,OAAML,eAAe,CAACO,kBAAhB,CAAmCF,CAAnC,CAAN;MAAA,CAAnB;IACA;;IACD,OAAOF,KAAK,CAACG,OAAN,CAAcD,CAAd,CAAP;EACA,CALwC,EAKtC,CACFL,eADE,EAEFG,KAFE,CALsC,CAAzC;EAUA,OAAOC,qBAAP;AACA"}