In practice the MELS-1,2,3 solves nothing, revert it
This commit is contained in:
parent
6fead66f89
commit
f92708fbe6
1 changed files with 4 additions and 5 deletions
|
@ -237,7 +237,6 @@ module.exports = React.createClass({
|
||||||
this.eventNodes = {};
|
this.eventNodes = {};
|
||||||
|
|
||||||
var i;
|
var i;
|
||||||
let melsIndex = 0;
|
|
||||||
|
|
||||||
// first figure out which is the last event in the list which we're
|
// first figure out which is the last event in the list which we're
|
||||||
// actually going to show; this allows us to behave slightly
|
// actually going to show; this allows us to behave slightly
|
||||||
|
@ -303,10 +302,10 @@ module.exports = React.createClass({
|
||||||
// instead will allow new props to be provided. In turn, the shouldComponentUpdate
|
// instead will allow new props to be provided. In turn, the shouldComponentUpdate
|
||||||
// method on MELS can be used to prevent unnecessary renderings.
|
// method on MELS can be used to prevent unnecessary renderings.
|
||||||
//
|
//
|
||||||
// melsIndex is deliberately unrelated to the contained events so that pagination
|
// Whilst back-paginating with a MELS at the top of the panel, prevEvent will be null,
|
||||||
// will not cause it to be recreated.
|
// so use the key "membereventlistsummary-initial". Otherwise, use the ID of the first
|
||||||
const key = "membereventlistsummary-" + melsIndex;
|
// membership event, which will not change during forward pagination.
|
||||||
melsIndex++;
|
const key = "membereventlistsummary-" + (prevEvent ? mxEv.getId() : "initial");
|
||||||
|
|
||||||
if (this._wantsDateSeparator(prevEvent, mxEv.getDate())) {
|
if (this._wantsDateSeparator(prevEvent, mxEv.getDate())) {
|
||||||
let dateSeparator = <li key={ts1+'~'}><DateSeparator key={ts1+'~'} ts={ts1}/></li>;
|
let dateSeparator = <li key={ts1+'~'}><DateSeparator key={ts1+'~'} ts={ts1}/></li>;
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue