Linter fix post merge conflicts
This commit is contained in:
@ -28,7 +28,6 @@ export const RecordTableBodyEffect = () => {
|
|||||||
setRecordTableData,
|
setRecordTableData,
|
||||||
loading,
|
loading,
|
||||||
queryStateIdentifier,
|
queryStateIdentifier,
|
||||||
cursorsByRecordId,
|
|
||||||
} = useLoadRecordIndexTable(objectNameSingular);
|
} = useLoadRecordIndexTable(objectNameSingular);
|
||||||
|
|
||||||
const isFetchingMoreObjects = useRecoilValue(
|
const isFetchingMoreObjects = useRecoilValue(
|
||||||
@ -122,7 +121,7 @@ export const RecordTableBodyEffect = () => {
|
|||||||
if (!loading) {
|
if (!loading) {
|
||||||
setRecordTableData(records, totalCount);
|
setRecordTableData(records, totalCount);
|
||||||
}
|
}
|
||||||
}, [records, totalCount, setRecordTableData, loading, cursorsByRecordId]);
|
}, [records, totalCount, setRecordTableData, loading]);
|
||||||
|
|
||||||
const fetchMoreDebouncedIfRequested = useDebouncedCallback(async () => {
|
const fetchMoreDebouncedIfRequested = useDebouncedCallback(async () => {
|
||||||
// We are debouncing here to give the user some room to scroll if they want to within this throttle window
|
// We are debouncing here to give the user some room to scroll if they want to within this throttle window
|
||||||
|
|||||||
Reference in New Issue
Block a user