You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
which, when Paginator prop is used, constructs two instances of Paginator, one from findTypes (called by getFirst) and the one used for the defaultValue passed into getFirst.
should we be using the third argument rather than doing something like:
yes this seems like a good way to improve performance. In most cases, elements created are really minimal component wrappers with render: () => null so creating elements from these components normally don't cause performance issues, but since it's not always the case, using more short-circuit evaluation like you suggest can only make things better.
jhsu
pushed a commit
to jhsu/lucid
that referenced
this issue
Jan 22, 2018
usually requires something like:
which, when Paginator prop is used, constructs two instances of Paginator, one from
findTypes
(called bygetFirst
) and the one used for the defaultValue passed intogetFirst
.should we be using the third argument rather than doing something like:
so that only one element is ever created?
The text was updated successfully, but these errors were encountered: