-
I started playing around with Refine today before possible adoption. I like it, but there's one impending question. At first glance, refine seems to be very opinionated on data fetches. For example: const { data, isLoading } = useList<IAccount>({
resource: 'accounts/Internal/v1/Accounts',
config: {
// pagination: { page: 0, pageSize: 10 }
hasPagination: false,
filters: [
{
field: 'page',
operator: 'eq',
value: 0
},
{
field: 'pageSize',
operator: 'eq',
value: 10
}
]
},
queryOptions: {
enabled: true,
staleTime: Clock.Minute
}
}) While you follow the standards for "cursor-based" pagination and 're having an incredible utility hooks library.
|
Beta Was this translation helpful? Give feedback.
Answered by
vinclou
Aug 5, 2022
Replies: 1 comment
-
It would be nice if the Pagination was generic but could be solved by the custom data provider while dealing with the current prop. |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
vinclou
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be nice if the Pagination was generic but could be solved by the custom data provider while dealing with the current prop.