I do see your point and I think the code you use on a project should be balanced by the architects controlling it.
Our main app uses this and a <VirtualRepeat> that has the same signature but lets you specify a number of visible items and it's nice because everyone knows them and can swap between them as necessary - however - it does require training and would not work well in many circumstances. Also we use the version that does <Repeat list={blah} item={<SomeItem blahblah={doSomething}/>} /> over the one that uses it as a child.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I do see your point and I think the code you use on a project should be balanced by the architects controlling it.
Our main app uses this and a
<VirtualRepeat>that has the same signature but lets you specify a number of visible items and it's nice because everyone knows them and can swap between them as necessary - however - it does require training and would not work well in many circumstances. Also we use the version that does<Repeat list={blah} item={<SomeItem blahblah={doSomething}/>} />over the one that uses it as a child.