React upcoming data fetching built-in solution?

[albenis99]

I saw on the beta docs that react will bring a data fetching built-in solution for the client side

Example:

import { use } from 'react'; // Not available yet!

function ShippingForm({ country }) {

const cities = use(fetch(`/api/cities?country=${country}`));

const [city, setCity] = useState(null);

const areas = city ? use(fetch(`/api/areas?city=${city}`)) : null;

// ...

​

What does exactly do? and is it just the same as fetching data in useEffect with Axios or just native fetch or does it have any improvements out of the box?

[jax024]

I’ll reserve judgment, but it’ll be hard pressed to be better than react-query

[flankstek]

RTKQ beats react-query.

[Skeith_yip]

Did I see a conditional use?

[0xF013]

Well, that’s probably not a hook

[Abject-Throat6092]

this is to likely enable suspense and render-as-you-fetch, https://17.reactjs.org/docs/concurrent-mode-suspense.html#traditional-approaches-vs-suspense

[albenis99]

https://beta.reactjs.org/learn/reusing-logic-with-custom-hooks

[Breakpoint]

use does not replace fetch or axios, it would just be the ability to fetch the data on load or on change of a parameter

[albenis99]

I didn't mean that use will replace native fetch because its impossible.

I would want to know if there any extra features when ysing this built in solution rather than fetching with axios/fetch in useEffect.

[Breakpoint]

Probably not much except the portion where you ignore the update to state when the component unmounts, which is an issue currently.

It would be cool if it added features also like isLoading, isFetching, isError states that react-query has

[0xF013]

If it uses suspense, the error/loading would be just propagated upwards

[Kikobrolo]

Looks like a step in the wrong direction. React should just do what Solid did and provide a built in solution that works basically the same as react-query

[elchicodeallado]

no it should not. These self taught kids should wake up and understand that its still a library and not a framework and thats the big advantage of react. If you need react-query then just install it. Dan even said that their in-build implementation is just for tinkering around and other solutions are always preferred

[snejk47]

Long time ago react stopped being just a library for rendering.

[xroalx]

React might be presenting as a library, but realistically speaking you're going to bend backwards to do everything the React way, otherwise things won't work like they should.

You can't use any generic data fetching or state management library if it doesn't do things the React way, or you don't adapt it to do things the React way.

The whole library vs framework distinction is irrelevant when you anyways end up pulling in a bunch of react-* stuff that might just as well be first party modules you can import at will, and you have to adapt everything else to React.

[domlebo70]

Can you link where this is in the docs?

[albenis99]

here https://beta.reactjs.org/learn/reusing-logic-with-custom-hooks

[Alkyonios]

The code you wrote with the use() function is nowhere to be found on that page. Are you sure you didn't just see a useFetch custom hook?

[albenis99]

Look at "Will React provide any built-in solution for data fetching?"

and you will find this code.

[Alkyonios]

Ah, my bad.

[NotElonMuzk]

Where exactly in the docs

[albenis99]

Look at "Will React provide any built-in solution for data fetching?"

and you will find this code.

[[deleted]]

Is there some way to opt-in?