Matija Sosic

@cursorial that would be awesome! I will now be building out the skeleton and then you are more than welcome to join on the frontend side :).

Waspello v1.0 (or maybe rather v0.1 :D) is out! You can see it in action at https://waspello.netlify.app/ and check the source code at [examples/waspello](https://github.com/wasp-lang/wasp/tree/master/examples/waspello). Below is the list of features...

@cursorial are you still interested in working on Waspello frontend? Would be great to get your input now that we have v1!

@vicnicius @cursorial of course, sounds great! @vicnicius let me know what you'd like to take on and I am also happy to help you start or answer any questions. @cursorial...

I did some initial reading on optimistic UI updates (updating what query returns without refetching it), so here are some first thoughts. It seems to me there are three main...

All makes sense @Martinsos! I've just been investigating what can be done with `react-query`, here is what I learned in short: In `react-query`, when defining a mutation, a developer has...

Re explicit local state - this is how things currently work (no explicit state): ```js const MainPage = ({ user }) => { // react-query ensures reactivity. const { data:...

If we start with the most simplistic approach, just trying to provide the most direct interface to `react-query`'s `onMutate()`, I figured it would look something like this in Wasp: main.wasp:...

@Martinsos good question about the `onMutate()` - I check the docs and turns out it runs before the mutation function is executed. Although, theoretically, we could update query cache either...

https://github.com/wasp-lang/wasp/issues/870 -> opened this one, but turned out to be a duplicate.