-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEAT] Add a dataprovider using KY #6381
Comments
@capsloq thanks for the issue. About exposing it as https://github.com/refinedev/refine/blob/master/packages/nextjs-router/package.json |
hey @BatuhanW , I am working on adding the KY data provider to the |
@OmkarBansod02 Nice! I can help with testing if you want |
@kfern Yeah sure! i have open a PR. once go through it. |
We will update the issue with more details about the implementation we want after discussing with the core team. |
Is your feature request related to a problem? Please describe.
Most data providers use of Axios which is considered deprecated by (many/some). See adios-axios. Nowadays Native Fetch APIs are widely supported by all big browsers. A thin wrapper like
KY
provides an easy API to make use of functionalities like interceptors.Describe alternatives you've considered
No response
Additional context
Axios was once a convenient library that utilized XMLHttpRequest in web browsers and the http module in Node environments. However, in today's modern development landscape, this approach has been surpassed by the native Fetch API, which offers consistent functionality across browsers, Node, and even other environments.
With the adoption of a unified API like Fetch, you can easily eliminate Axios as an additional dependency in your modern codebase, resulting in reduced bundle sizes. Moreover, the Fetch API has undergone full standardization, unlike Axios, which comes with its own set of nuances that often catch developers off-guard. This includes differences in how fetch and Axios handle promise rejection in various scenarios.
Furthermore, certain frameworks, like Next.js, have begun exposing additional features within the Fetch API that may not be readily accessible when using Axios.
Discussion was started here:
#6375 (reply in thread)
Issue was opened for better tracking.
Describe the thing to improve
Add ky support
@refinedev/simple-rest/ky
Once the simple-rest-ky provider is implemented it might be used as a blueprint for upcoming providers e.g. Strapi 5
The text was updated successfully, but these errors were encountered: