Issue 1:
Describe what you were doing when the bug occurred:

1.

2.

3.

Please do not remove the text below this line

DevTools version: 4.10.1-f160547f47

Call stack: at store_Store.getElementAtIndex (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:21226:35)

at store_Store.getElementIDAtIndex (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:21242:26)

at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:28678:63

at List.render (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:22934:18)

at vi (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:13515:76)

at ui (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:13506:10)

at mk (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:16077:86)

at lk (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:15459:11)

at kk (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:15451:23)

at ck (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:15435:5)

Component stack: at List (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:22629:30)

at div

at AutoSizer (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:3003:5)

at div

at div

at Tree_Tree (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:28429:47)

at div

at div

at InspectedElementContextController (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:28921:3)

at OwnersListContextController (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:27558:3)

at SettingsModalContextController (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:28206:3)

at Components_Components (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:33383:52)

at ErrorBoundary_ErrorBoundary (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:29219:5)

at PortaledContent (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:29336:32)

at div

at div

at ProfilerContextController (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:32934:3)

at TreeContextController (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:24322:3)

at SettingsContextController (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:24811:3)

at ModalDialogContextController (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:29404:3)

at DevTools_DevTools (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:36207:3)

Issue 2:
I would also like to propose that following potentially improvements for speed and simplicity now that useState is there.

I would like to propose the following variants, which introduce a modstamp and a setItem for state that contains list of items.

Instead of having to destructor arrays and objects and things to cause reference changes, which is havey,

setItem would implicit tick the mostamp for an item in an array and the modstamp if required at array container level.

There would be alot less overhead in my mind to this approach that to setItem([...this.array]), causing new references to be created in the back ground, such that there is a reference change detected, such that item re-renders.

if one wants to do a bulk update with more than a single item then setContent(this.array), which implicit, tick the mostamp.

This would simplify things, because everything is basically reduce to a primative comparison or modstamp and no doesn't need to write deep ShouldComponentUpdate comparison anymore, as been take into account by useState.

I think it is quite straint forward, obviously there would be all the logic in the background wrapping useState or using symbol and inject directly into an object. One just needs a GetContent the with out a modstamp for hitting API's.

Typically this is just a concept, the function names and useState variants don't have to follow everything word for word names and that are menings less, its basically behavior, simplification that one is looking for, weather is with effects or which every.

Typically UseState approach is much nicer, when having to setup, things, where on is linking into to nested structures of this.state, because updating them requires destructing of parent properties, such that they not lost.

Continuous Scroll

In addition to this one also is there required the ability to not tick the timestamp when setContent is used, because when you working with controls where the is a data provide for like FlatList or things like that, where only UI items for screens space, while all data is not converted into controls, only the section for display. Typiclaly the documentation with regards to react-native is not correctly in how to use js for continuous scroll, as par last docs I read, cause full re-renders instead appends, for data off screen. Depends on weather you have a full screen of items or less basically. Basically flatList could also detect not just reference change, but array exceeding being below the minimum number of row Items that would cover the screen. if is an append, well change is ignored. If update, then mostamps would have change for the person.

CRUD system of changes

Basically you could also implement Create/Update/Delete item delta caching in the back ground for aggregation, which what I ultimate wanted to do in missive cad system, to reduce UI re-draw. I this case just before render, deltas are then merge before GetDerivedStateFromProps and render would be called.

const modStamp = Symbol('modstamp');

enum UseStateType {
Primative,
ArrayObject,
Object
}

// Different function names could be used as well.
useState(type: UseStateType, initialcontent: TLookUpValueType, setMethod?: (value: TLookUpValueType) => void)) : any
useState(UseStateType.Primative, initialcontent: TLookUpValueType, setMethod?: (value: TLookUpValueType) => void)) : [
setContent, getContent]

useState(UseStateType.ArrayObject, initialcontent: TLookUpValueType, setMethod? :(value: TLookUpValueType) => void)) : [
setContent, setItem, ,getContent, getModStamp, tickModStamp]

useState(UseStateType.Object, initialcontent: TLookUpValueType, setMethod? :(value: TLookUpValueType) => void)) : [
setContent, setItem, ,getContent, getModStamp, tickModStamp] {

const setItem = (pos, item) => {
item[modStamp] = (this.state.array[pos][modStamp] || 0)++;
this.state.array[pos] = item;
}

return [.., setItem, .. , ..];
}

render () {

return <React.Fragment>
this.state.map(it => <Item key={it.key} modStamp={it.modStamp} value={it}>
</React.Fragment>
}