Maximilian Fischer
Maximilian Fischer
The failing test is fixed as part of #734.
It might be a problem with the relation. I don't even know if relations currently work. #416 Edit: Is your query working when using it without the ParseLiveListWidget?
It's a mix, I guess. Maybe more of a bug fix, since the parameters already exist and are just not used (bug).
> it's missing a changelog entry Sorry, thought we want to create it automatically for the next release.
Since it won't be published to pub.dev (I think regardless of `.pubignore`, but I'm not sure about that.) it's just a development thing. From that perspective: +1 for your argumentation...
But isn't Future the Response wrapper already? Of course we could achieve type safety with generics, too. But as the Response class has the field `result` as well as `results`,...
I might start implementing some parts. Then we can have a look if it's worth it.
I've found no time implementing this in a test-branch, but I will give this a try in the future. In many cases using [extensions](https://dart.dev/guides/language/extension-methods) helps to reduce unwrapping. ```dart import...
Same for `scrollPhysics`, `scrollController`, `shrinkWrap`... Your PR got closed since we deleted the development branch. It's not because of your changes.
registerSubclass would be great. Maybe changing fomJson in ParseBase could do the trick. Any ideas?