Overview - Table

7 days30 days

Latest CI Pipeline Executions

Fuzzy

In progress
6532
0f7fd347 still skip autoResetPageIndex in controlled state scenarios
by Kevin Van ...
Succeeded
6532
cbf40f8e address stale updater bug, simplify
by Kevin Van ...
Succeeded
6532
c7d1f94b omit row selection from new check
by Kevin Van ...
Succeeded
6532
c7d1f94b omit row selection from new check
by Kevin Van ...
Canceled
6532
c7d1f94b omit row selection from new check
by Kevin Van ...
Failed
6532
Fix ready→
c7d1f94b omit row selection from new check
by Kevin Van ...
Canceled
6532
c7d1f94b omit row selection from new check
by Kevin Van ...
Succeeded
6532
c00a5dd2 add date filters to filter examples
by Kevin Van ...
Succeeded
6532
c00a5dd2 add date filters to filter examples
by Kevin Van ...
Succeeded
6532
34ac8623 refactor(table-core): centralize no-op state update guarding in setStateSlice Route every table.setX state router through a single setStateSlice util that resolves the updater once against the slice's current value, structurally compares the result, and skips the onXChange handler entirely when nothing changed. This removes the class of render loops where auto resets fired change handlers with freshly allocated but semantically identical values (e.g. autoResetExpanded after a data reference change), and deletes the scattered ad-hoc guards that previously protected individual slices. For uncontrolled slices the default handler receives the pre-resolved value, so updaters run exactly once. User handlers and externally owned slices receive the original updater untouched to preserve functional update composition and independent base-atom fallback semantics. Supersedes #6519. Co-Authored-By: Dmitrii Kartashev <dikartashev@gmail.com> Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
by Kevin Van ...
Failed
6532
Fix ready→
34ac8623 refactor(table-core): centralize no-op state update guarding in setStateSlice Route every table.setX state router through a single setStateSlice util that resolves the updater once against the slice's current value, structurally compares the result, and skips the onXChange handler entirely when nothing changed. This removes the class of render loops where auto resets fired change handlers with freshly allocated but semantically identical values (e.g. autoResetExpanded after a data reference change), and deletes the scattered ad-hoc guards that previously protected individual slices. For uncontrolled slices the default handler receives the pre-resolved value, so updaters run exactly once. User handlers and externally owned slices receive the original updater untouched to preserve functional update composition and independent base-atom fallback semantics. Supersedes #6519. Co-Authored-By: Dmitrii Kartashev <dikartashev@gmail.com> Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
by Kevin Van ...
Canceled
6532
34ac8623 refactor(table-core): centralize no-op state update guarding in setStateSlice Route every table.setX state router through a single setStateSlice util that resolves the updater once against the slice's current value, structurally compares the result, and skips the onXChange handler entirely when nothing changed. This removes the class of render loops where auto resets fired change handlers with freshly allocated but semantically identical values (e.g. autoResetExpanded after a data reference change), and deletes the scattered ad-hoc guards that previously protected individual slices. For uncontrolled slices the default handler receives the pre-resolved value, so updaters run exactly once. User handlers and externally owned slices receive the original updater untouched to preserve functional update composition and independent base-atom fallback semantics. Supersedes #6519. Co-Authored-By: Dmitrii Kartashev <dikartashev@gmail.com> Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
by Kevin Van ...