virtual-scroller 1.11.1 → 1.11.3

package/source/react/useState.js

@@ -1,113 +1,98 @@
-import { useState, useRef, useLayoutEffect } from 'react'
+import { useState, useRef, useCallback, useLayoutEffect } from 'react'
 
 // Creates state management functions.
-export default function _useState({ initialState, onRender, items }) {
-	// `VirtualScroller` state.
+export default function _useState({
+	initialState,
+	onRender,
+	itemsProperty,
+	USE_ITEMS_UPDATE_NO_SECOND_RENDER_OPTIMIZATION
+}) {
+	// 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.
 	//
-	// The `_stateUpdate` variable shouldn't be used directly
-	// because in some cases its value may not represent
-	// the actual `state` of the `VirtualScroller`.
+	// It will also be stale in cases when `USE_ITEMS_UPDATE_NO_SECOND_RENDER_OPTIMIZATION`
+	// feature is used for setting new `items` in state.
 	//
-	// * It will contain an incorrect initial value if `initialState` property is passed
-	//   because it doesn't get initialized to `initialState`.
-	//
-	// * If `items` property gets changed, `state` reference variable gets updated immediately
-	//   but the `_stateUpdate` variable here doesn't (until the component re-renders some other time).
-	//
-	// Instead, use the `state` reference below.
-	//
-	const [_stateUpdate, _setStateUpdate] = useState()
+	const [_newState, _setNewState] = useState(initialState)
 
-	// This `state` reference is used for accessing the externally stored
-	// virtual scroller state from inside a `VirtualScroller` instance.
-	//
-	// It's also the "source of truth" on the actual `VirtualScroller` state.
-	//
+	// This `state` reference is what `VirtualScroller` uses internally.
+	// It's the "source of truth" on the actual `VirtualScroller` state.
 	const state = useRef(initialState)
 
-	// Accumulates state updates until they have been applied.
-	const targetState = useRef(initialState)
+	const setState = useCallback((newState) => {
+		state.current = newState
+	}, [])
 
-	// Update the current state reference.
-	//
-	// Ignores the cases when `state` reference has already been updated
-	// "immediately" bypassing a `_setStateUpdate()` call, because
-	// in that case, `_stateUpdate` holds a stale value.
-	//
-	if (state.current !== targetState.current) {
-		state.current = _stateUpdate
-	}
+	// Accumulates all "pending" state updates until they have been applied.
+	const nextState = useRef(initialState)
 
-	// Call `onRender()` right after every state update.
-	//
-	// When `items` property changes, `useHandleItemsChange()` hook doesn't call
-	// `_setStateUpdate()` because there's no need for a re-render.
-	// But chaning `items` still does trigger a `VirtualScroller` state update,
-	// so added `items` property in the list of this "effect"'s dependencies.
-	//
+	// Updates the actual `VirtualScroller` state right after a requested state update
+	// has been applied. Doesn't do anything at initial render.
+	useLayoutEffect(() => {
+		setState(_newState)
+	}, [
+		_newState
+	])
+
+	// Calls `onRender()` right after every state update (which is a re-render),
+	// and also right after the initial render.
 	useLayoutEffect(() => {
 		onRender()
 	}, [
-		_stateUpdate,
-		items
+		_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
 	])
 
 	return {
 		getState: () => state.current,
 
-		// Updates existing state.
+		getNextState: () => nextState.current,
+
+		// Requests a state update.
 		//
-		// State updates are incremental meaning that this code should mimick
+		// State updates are incremental meaning that this function mimicks
 		// the classic `React.Component`'s `this.setState()` behavior
-		// when calling `this.setState()` doesn't replace `state` but rather merges
-		// a set of the updated state properties with the rest of the old ones.
+		// when calling `this.setState()` didn't replace `state` but rather merged
+		// the updated state properties over the "old" state properties.
 		//
-		// The reason is that `useState()` updates are "asynchronous" (not immediate),
+		// 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 the state updates.
+		// before the state actually updates, resulting in losing some of those state updates.
 		//
-		// For example, the first `updateState()` call updates shown item indexes,
+		// 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.
 		//
-		// Using `...state.current` instead of `...pendingState.current` here
-		// would produce "stale" results.
-		//
 		updateState: (stateUpdate) => {
-			const newState = {
-				...targetState.current,
+			nextState.current = {
+				...nextState.current,
 				...stateUpdate
 			}
-			targetState.current = newState
-			// If `items` property did change the component detects it at render time
-			// and updates `VirtualScroller` items immediately by calling `.setItems()`.
-			// But, since all of that happens at render time and not in an "effect",
-			// if the state update was done as usual by calling `_setStateUpdate()`,
-			// React would throw an error about updating state during render.
-			// Hence, state update in that particular case should happen "directly",
-			// without waiting for an "asynchronous" effect to trigger and call
-			// an "asyncronous" `_setStateUpdate()` function.
-			//
-			// Updating state directly in that particular case works because there
-			// already is a render ongoing, so there's no need to re-render the component
-			// again after such render-time state update.
+			// 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 an `.items`
+			// 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.
 			//
-			if (stateUpdate.items) {
-				// If a `stateUpdate` contains `items` then it means that there was a `setItems()` call.
-				// No need to trigger a re-render — the component got re-rendered anyway.
-				// Just update the `state` "in place".
-				state.current = newState
+			const _newState = nextState.current
+			if (stateUpdate.items && USE_ITEMS_UPDATE_NO_SECOND_RENDER_OPTIMIZATION) {
+				setState(_newState)
 			} else {
-				_setStateUpdate(newState)
+				_setNewState(_newState)
 			}
 		}
 	}

package/source/react/useStyle.js

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

package/commonjs/react/useHandleItemsChange.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"useHandleItemsChange.js","names":["useHandleItemsChange","items","virtualScroller","preserveScrollPosition","preserveScrollPositionOnPrependItems","updateItemKeysForNewItems","getState","renderedItems","firstShownItemIndex","previousItems","useRef","hasItemsPropertyChanged","current","itemsHaveChanged","shouldUpdateItemKeys","itemsDiff","getItemsDiff","prependedItemsCount","appendedItemsCount","setItems"],"sources":["../../source/react/useHandleItemsChange.js"],"sourcesContent":["import { useRef } from 'react'\r\n\r\n// If new `items` are 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\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 useHandleItemsChange(items, {\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\tupdateItemKeysForNewItems\r\n}) {\r\n\tconst {\r\n\t\titems: renderedItems,\r\n\t\tfirstShownItemIndex\r\n\t} = virtualScroller.getState()\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 previousItems = useRef(items)\r\n\tconst hasItemsPropertyChanged = items !== previousItems.current\r\n\tpreviousItems.current = items\r\n\tif (hasItemsPropertyChanged) {\r\n\t\tlet itemsHaveChanged = true\r\n\t\tlet shouldUpdateItemKeys = true\r\n\t\tconst itemsDiff = virtualScroller.getItemsDiff(renderedItems, items)\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 haven't changed. No need to re-generate\r\n\t\t\t\t// the `key` prefix or to snapshot the Y scroll position.\r\n\t\t\t\titemsHaveChanged = false\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// Just some items got appended. No need to re-generate\r\n\t\t\t\t// the `key` prefix or to snapshot the Y scroll position.\r\n\t\t\t\tshouldUpdateItemKeys = false\r\n\t\t\t}\r\n\t\t}\r\n\r\n\t\tif (itemsHaveChanged) {\r\n\t\t\t// Set the new `items`.\r\n\t\t\tvirtualScroller.setItems(items, {\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\r\n\t\t\t// Update React element `key`s for the new set of `items`.\r\n\t\t\tif (shouldUpdateItemKeys) {\r\n\t\t\t\tupdateItemKeysForNewItems()\r\n\t\t\t}\r\n\t\t}\r\n\t}\r\n}"],"mappings":";;;;;;;AAAA;;AAEA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACA;AACe,SAASA,oBAAT,CAA8BC,KAA9B,QAOZ;EAAA,IANFC,eAME,QANFA,eAME;EAAA,IAHFC,sBAGE,QAHFA,sBAGE;EAAA,IAFFC,oCAEE,QAFFA,oCAEE;EAAA,IADFC,yBACE,QADFA,yBACE;;EACF,4BAGIH,eAAe,CAACI,QAAhB,EAHJ;EAAA,IACQC,aADR,yBACCN,KADD;EAAA,IAECO,mBAFD,yBAECA,mBAFD,CADE,CAMF;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,aAAa,GAAG,IAAAC,aAAA,EAAOT,KAAP,CAAtB;EACA,IAAMU,uBAAuB,GAAGV,KAAK,KAAKQ,aAAa,CAACG,OAAxD;EACAH,aAAa,CAACG,OAAd,GAAwBX,KAAxB;;EACA,IAAIU,uBAAJ,EAA6B;IAC5B,IAAIE,gBAAgB,GAAG,IAAvB;IACA,IAAIC,oBAAoB,GAAG,IAA3B;IACA,IAAMC,SAAS,GAAGb,eAAe,CAACc,YAAhB,CAA6BT,aAA7B,EAA4CN,KAA5C,CAAlB,CAH4B,CAI5B;;IACA,IAAIc,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;QACAL,gBAAgB,GAAG,KAAnB;QACAC,oBAAoB,GAAG,KAAvB;MACA,CALD,MAMK,IAAIG,mBAAmB,KAAK,CAAxB,IAA6BC,kBAAkB,GAAG,CAAtD,EAAyD;QAC7D;QACA;QACAJ,oBAAoB,GAAG,KAAvB;MACA;IACD;;IAED,IAAID,gBAAJ,EAAsB;MACrB;MACAX,eAAe,CAACiB,QAAhB,CAAyBlB,KAAzB,EAAgC;QAC/B;QACA;QACAG,oCAAoC,EAAEA,oCAAoC,IAAID;MAH/C,CAAhC,EAFqB,CAQrB;;MACA,IAAIW,oBAAJ,EAA0B;QACzBT,yBAAyB;MACzB;IACD;EACD;AACD"}

package/commonjs/react/useOnItemHeightChange.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"useOnItemHeightChange.js","names":["useOnItemHeightChange","items","virtualScroller","initialCacheValue","useMemo","Array","length","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\titems,\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(items.length)\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,KAEE,QAFFA,KAEE;EAAA,IADFC,eACE,QADFA,eACE;EACF;EACA,IAAMC,iBAAiB,GAAG,IAAAC,cAAA,EAAQ,YAAM;IACvC,OAAO,IAAIC,KAAJ,CAAUJ,KAAK,CAACK,MAAhB,CAAP;EACA,CAFyB,EAEvB,EAFuB,CAA1B,CAFE,CAMF;;EACA,IAAMC,KAAK,GAAG,IAAAC,aAAA,EAAOL,iBAAP,CAAd,CAPE,CASF;EACA;;EACA,IAAMM,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,OAAMT,eAAe,CAACW,kBAAhB,CAAmCF,CAAnC,CAAN;MAAA,CAAnB;IACA;;IACD,OAAOJ,KAAK,CAACK,OAAN,CAAcD,CAAd,CAAP;EACA,CAL6B,EAK3B,CACFT,eADE,EAEFK,KAFE,CAL2B,CAA9B;EAUA,OAAOE,qBAAP;AACA"}

package/modules/react/useHandleItemsChange.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"useHandleItemsChange.js","names":["useRef","useHandleItemsChange","items","virtualScroller","preserveScrollPosition","preserveScrollPositionOnPrependItems","updateItemKeysForNewItems","getState","renderedItems","firstShownItemIndex","previousItems","hasItemsPropertyChanged","current","itemsHaveChanged","shouldUpdateItemKeys","itemsDiff","getItemsDiff","prependedItemsCount","appendedItemsCount","setItems"],"sources":["../../source/react/useHandleItemsChange.js"],"sourcesContent":["import { useRef } from 'react'\r\n\r\n// If new `items` are 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\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 useHandleItemsChange(items, {\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\tupdateItemKeysForNewItems\r\n}) {\r\n\tconst {\r\n\t\titems: renderedItems,\r\n\t\tfirstShownItemIndex\r\n\t} = virtualScroller.getState()\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 previousItems = useRef(items)\r\n\tconst hasItemsPropertyChanged = items !== previousItems.current\r\n\tpreviousItems.current = items\r\n\tif (hasItemsPropertyChanged) {\r\n\t\tlet itemsHaveChanged = true\r\n\t\tlet shouldUpdateItemKeys = true\r\n\t\tconst itemsDiff = virtualScroller.getItemsDiff(renderedItems, items)\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 haven't changed. No need to re-generate\r\n\t\t\t\t// the `key` prefix or to snapshot the Y scroll position.\r\n\t\t\t\titemsHaveChanged = false\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// Just some items got appended. No need to re-generate\r\n\t\t\t\t// the `key` prefix or to snapshot the Y scroll position.\r\n\t\t\t\tshouldUpdateItemKeys = false\r\n\t\t\t}\r\n\t\t}\r\n\r\n\t\tif (itemsHaveChanged) {\r\n\t\t\t// Set the new `items`.\r\n\t\t\tvirtualScroller.setItems(items, {\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\r\n\t\t\t// Update React element `key`s for the new set of `items`.\r\n\t\t\tif (shouldUpdateItemKeys) {\r\n\t\t\t\tupdateItemKeysForNewItems()\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;AACA;AACA;AACA;AACA;AACA;AACA;;AACA,eAAe,SAASC,oBAAT,CAA8BC,KAA9B,QAOZ;EAAA,IANFC,eAME,QANFA,eAME;EAAA,IAHFC,sBAGE,QAHFA,sBAGE;EAAA,IAFFC,oCAEE,QAFFA,oCAEE;EAAA,IADFC,yBACE,QADFA,yBACE;;EACF,4BAGIH,eAAe,CAACI,QAAhB,EAHJ;EAAA,IACQC,aADR,yBACCN,KADD;EAAA,IAECO,mBAFD,yBAECA,mBAFD,CADE,CAMF;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,aAAa,GAAGV,MAAM,CAACE,KAAD,CAA5B;EACA,IAAMS,uBAAuB,GAAGT,KAAK,KAAKQ,aAAa,CAACE,OAAxD;EACAF,aAAa,CAACE,OAAd,GAAwBV,KAAxB;;EACA,IAAIS,uBAAJ,EAA6B;IAC5B,IAAIE,gBAAgB,GAAG,IAAvB;IACA,IAAIC,oBAAoB,GAAG,IAA3B;IACA,IAAMC,SAAS,GAAGZ,eAAe,CAACa,YAAhB,CAA6BR,aAA7B,EAA4CN,KAA5C,CAAlB,CAH4B,CAI5B;;IACA,IAAIa,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;QACAL,gBAAgB,GAAG,KAAnB;QACAC,oBAAoB,GAAG,KAAvB;MACA,CALD,MAMK,IAAIG,mBAAmB,KAAK,CAAxB,IAA6BC,kBAAkB,GAAG,CAAtD,EAAyD;QAC7D;QACA;QACAJ,oBAAoB,GAAG,KAAvB;MACA;IACD;;IAED,IAAID,gBAAJ,EAAsB;MACrB;MACAV,eAAe,CAACgB,QAAhB,CAAyBjB,KAAzB,EAAgC;QAC/B;QACA;QACAG,oCAAoC,EAAEA,oCAAoC,IAAID;MAH/C,CAAhC,EAFqB,CAQrB;;MACA,IAAIU,oBAAJ,EAA0B;QACzBR,yBAAyB;MACzB;IACD;EACD;AACD"}

package/modules/react/useOnItemHeightChange.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"useOnItemHeightChange.js","names":["useMemo","useRef","useCallback","useOnItemHeightChange","items","virtualScroller","initialCacheValue","Array","length","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\titems,\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(items.length)\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,KAEE,QAFFA,KAEE;EAAA,IADFC,eACE,QADFA,eACE;EACF;EACA,IAAMC,iBAAiB,GAAGN,OAAO,CAAC,YAAM;IACvC,OAAO,IAAIO,KAAJ,CAAUH,KAAK,CAACI,MAAhB,CAAP;EACA,CAFgC,EAE9B,EAF8B,CAAjC,CAFE,CAMF;;EACA,IAAMC,KAAK,GAAGR,MAAM,CAACK,iBAAD,CAApB,CAPE,CASF;EACA;;EACA,IAAMI,qBAAqB,GAAGR,WAAW,CAAC,UAACS,CAAD,EAAO;IAChD,IAAI,CAACF,KAAK,CAACG,OAAN,CAAcD,CAAd,CAAL,EAAuB;MACtBF,KAAK,CAACG,OAAN,CAAcD,CAAd,IAAmB;QAAA,OAAMN,eAAe,CAACQ,kBAAhB,CAAmCF,CAAnC,CAAN;MAAA,CAAnB;IACA;;IACD,OAAOF,KAAK,CAACG,OAAN,CAAcD,CAAd,CAAP;EACA,CALwC,EAKtC,CACFN,eADE,EAEFI,KAFE,CALsC,CAAzC;EAUA,OAAOC,qBAAP;AACA"}