Sergio Xalambrí

Results 130 comments of Sergio Xalambrí

Try just installing `npm i @grial/cli` instead of `npm i @grial/cli@latest`.

@XREvo check the code of the [rethinkdb connector](https://github.com/sergiodxa/grial/tree/master/connector-rethinkdb), there I used `@grial/utils` to read the `grial.config.js` and allow more customization. Also can you check about the usage of a pool...

I think it’s way easier to ignore the result than cancel it with the current state of fetching libraries

You could use `mutate` to fill the SWR cache with data before rendering if you now what you will need. ```js const data = await fetcher("/api/resource/1"); mutate("/api/resource/1", data, false); //...

@samsisle what you proposed is somehow possible right now: ```js function fetcher(...urls) { return Promise.all(url.map(url => fetch(url).then(res => res.json()))); } const { data } = useSWR(["/api/user", "/api/movies"], fetcher) const [user,...

@Svish I agree that ideally you should split your components and call it a day, however sometimes it's not possible to split things up. I'm using a beta version of...

@saitonakamura I'm not using it anymore, the beta version for this is really old too, way before v1 of SWR and I don't remember the version to use in the...

@quietshu have you thought more about this? I think it could be implemented manually per project using subscribe and custom hooks but maybe it could be integrated directly in SWR,...

The bound mutate is not a special function, only do this `(data, shouldRevalidate) => mutate(key,data, shouldRevalidate)` and pass the key of the hook. The source of true of SWR is...

By local it means the cached data (local is the browser, remote is the API), so you can call `mutate(key, newData, false)` to mutate the cached data without a revalidation,...