juandiago
juandiago
I faced this same problem today, what I end up doing was configuring the cache at the root `Query` with a `TypePolicy` for my particular query that ignores the `offset`...
Got hit by this too, `optimisticResult` only triggers an `update` when using the `Mutation` widget, not when using the client directly with the `mutate` method
I ended up not needing this functionality, but here's what I found for future reference: The mRegistrar member is always nil in the lookupKey function, so all invocations return nil...
Hitting the exact same issue with Gov clients, we did have access to dev tools for debugging, but everything was fine over there, console was clean, no network errors....any other...
Can confirm seeing this issue on MBP16 2019 with Intel UHD 630
Updating to Flutter 3.16.5(Dart 3.2.3) seems to fix the issue. I was using Flutter 3.13.5. Closing.
on closer examination, issue is still present on 3.16.5 EDIT: seems to be vscode related, I'll try to gather more information....
Glad to see I'm not the only one suffering from AI in everything. I do not want it on my terminal, it's really getting on my nerve when I try...
Got into this one this week, sharing my solution in case it helps anybody: ```dart @HiveType() class Question { @HiveField(1) String id @HiveField(2) bool allowSomething; Question({ @required this.id, this.allowSomething, })...