Is it ok to manage the Data completely outside of Table

[programm-ingovals]

I have a server side managed collection which uses Cursor based pagination and Filtering on a single property ( open/closed or all ).

I've had mixed success trying to force the cursor based pagination into the current pagination mechanism
using controlled paging so I tried to do it outside of the table ( meaning I don't use table.nextPage() ), I just update the data state that goes into the table.

Adding the simple filtering I thought maybe I'll just do the same. But I want to make sure I'm not breaking something obvious here.

export function ExampleTable() {
	const [pageInfo, setPageInfo] = useState<PageInfo>()
	const [totalCount, setTotalCount] = useState<number | undefined>(undefined)
	const [collection, setCollectionData] = useState<TheItem[]>([])

	const table = useReactTable({
		data: collection,
		columns,
		getCoreRowModel: getCoreRowModel(),
	  })

	  const { data, fetchMore } = useItemQuery({
		variables: {
		  filter: {
			state: 'All',
		  },
		  pagination: { limit: pageSize },
		},
	  })

	  useEffect(() => {
		setCollectionData(data?.items?.data || [])
		setPageInfo(data?.items?.pageInfo)
		setTotalCount(data?.items?.totalCount || -1)
	  }, [data])

	  const updatePaging = (dir: 'forward' | 'backward') => {
		fetchMore({
		  variables: {
			filter: {
			  state: 'All',
			},
			pagination:
			  dir === 'forward'
				? { limit: pageSize, after: pageInfo?.endCursor }
				: { limit: pageSize, before: pageInfo?.startCursor },
		  },
		}).then((res) => {
		  setCollectionData(res.data?.cases?.data || [])
		  setPageInfo(res.data?.cases?.pageInfo)
		  setTotalCount(res.data?.cases?.totalCount)
		})
	  }


	  ...
}

Notice I do not bother setting manualPagination option on the table even since I'm foregoing that alltogether.

Issue with trying to use the built in mechanism is that Cursor based has no basic concept of page index but I would need to keep hold on the state of the cursors, manage which direction we are paging in.
I'm thinking I could manage that using the onPaginationChange and check the old vs the new pageIndex, but I'm always managing the PageInfo state either way.