Eliya Cohen
Eliya Cohen
@golergka Thanks for the tip. And still, I'll try to draw a scenario where this can get out of hand. Take this code for example: ```ts const updateUserCashQuery= sql`UPDATE users...
Although I'm unfamiliar with how pgtyped works behind the scenes, let me know if there's a way I can contribute to this feature.
@adelsz that's a nice solution that will definitely solve a lot of problems. Although, I believe it will be harder to maintain hundreds of queries like these mainly because: 1....
@smallnamespace the problem is that pg-typed is not aware of the brand types, therefore it cannot autogenerate the typing with the brand types.
@SidIcarus Sorry but no. Webpack and Vite work differently, which would've made me put in lots of effort. If it helps, we eventually adopted incrementally React (which runs inside AngularJS)...
eslint-plugin-query: exhaustive-deps error not triggered when dependency is nested inside then/catch
Sorry, I totally forgot about this issue. @TkDodo I can implement that, but it would be a breaking change. Currently, we allow call expressions inside `queryFn` without explicitly set them...
eslint-plugin-query: exhaustive-deps error not triggered when dependency is nested inside then/catch
So problem still persists. What's the point of passing a value that is not serializable into a query key? you would still get stale closures, since `JSON.stringify(fn)` would result in...
@TkDodo should I update the rule to catch `useInfiniteQuery` as well?
@TkDodo since we removed `prefer-query-object-syntax`, should we close this issue?
Thanks @apjoseph I'm not in a hurry, so I guess I'll wait for official implementation. Thanks again for the workaround! 🙂