Moshe Dicker

I'm going to try experimenting with some sort of prefetching mechanism to this API before merging. I want to make sure that it's possible with the current API

`FutureOr` is also very annoying to work with. SynchronousFuture is also not recommended. I don't want to have any loading screen when items are prefetched. https://github.com/dart-lang/sdk/issues/50204 https://github.com/dart-lang/language/issues/3625 Seems that remi...

@simolus3 This is becoming a bigger and bigger PR. There are a few breaking changes too. I don't think it will be easy to review. I'm going to create 4...

The changes that would be breaking aren't drastic. They could wait for a 3.0. I didn't realize that you plan on making a migration to `macros`. I'm super excited. I'm...

Proposal we add a suffix `Model` to each `Dto`. We can make it customizable via config E.G Instead of `Person` it will be `PersonModel` This suffix will be customizable via...

@Carapacik How to you want to handle this?

> I haven't experienced a situation where I needed an old app version to communicate with an old function version. This might be uncommon, or maybe it's just something I...

The benefit to having a `FooRequest` and `FooResponse` be separate classes is that `id` won't be an optional param. It will be `int` on `FooResponse` and wont exists at all...

My only additional proposal is that this is placed in a one decorator on the `save` function and not all over the place: ```dart @fallbacks({ Student3:save3, Student4:save4, }) Future save(FunctionContext...

@marcglasberg I'm trying to find all the issues with it, because it seems too good to be true! But besides for these few issues, this seems awesome! My only opinion...