Eliya Cohen

@karlhorky @thdxr It was fundamentally changed since then (wsl2) I would recommend to give it another try. While I rarely work on Windows, when I do - it’s on wsl

@CoEliya @thdxr Was considering setting up WSL for students since Oct 2019 (first issue in the repo), but IIRC it was the complexity / non-native interop, various different incompatible setups that kept us from going down that road github.com/upleveled/syst…

can someone describe to me the setup a power user would have on windows for their terminal? i cannot get a setup im happy with

@karlhorky @thdxr Out of curiosity, why not WSL?

@thdxr We use a simple setup with Git Bash and Chocolatey for students, not sure if that works for you github.com/upleveled/syst…

@karlhorky Yes. Ideally it should add the ability to support helpers, fragments, custom annotations, and everything that is library-specific.

@CoEliya Nice! Would that mean support for helpers like the Postgres.js `sql(...)` helper and the Slonik helpers? github.com/ts-safeql/safe…

Just published SafeQL v4 roadmap. Would love to hear your thoughts. Link below

@karlhorky There's always room for improvement in the json/jsonb saga, but V4 aims to be more pluggable, off-loading the work for other library maintainers who want to add a custom integration with SafeQL.

@CoEliya Looking great, thanks for your continued effort here! 🚀 Do you think that better json / jsonb support will also be in v4? Or is that a bigger thing for later?

Thank you @calloc134 for sponsoring ❤️

@jamesacowling I tend to disagree here about SQL being inexpressive. In fact, it’s one of the most expressive language I’ve encountered. You’re right that it’s quite loose and unsafe, but not if you’re using proper tooling. This is one of the reasons I built SafeQL which is open source.

ORMs exist because SQL is inexpressive and has a bad type system. They don’t fix the underlying problems but do mask them somewhat. Raw SQL is too dangerous to use in large production app code though. *cough* find a DB that lets you express queries as real code.

@arktypeio Have you considered another API where it doesn’t throw an error in runtime when using something that can’t be translated to json schema? If I recall I wanted to use that but it sometimes threw an error when I used subtypes like email

Need JSON Schema for your validator? Just call toJsonSchema- it's built-in to every type👍

Would love to hear your thoughts on this (@TkDodo) github.com/TanStack/query…

This can be adjusted or turned off. Visit the docs for more info #connections-inferliterals-optional" target="_blank" rel="nofollow noopener">safeql.dev/api/#connectio…

SafeQL 3.6.0 is now inferring string literals by default 🚀✨

I'm literally speechless.... 🤯 @kuizinas 🙏

@calloc134 Thank you 🙏🏻

I just sponsored Newbie012. Go sponsor your open source dependencies! github.com/sponsors/Newbi… safeqlいつも使わせていただいております

@TkDodo @housecor @AArdvarkErick @tanstack/query/enforce-query-options?

@housecor @AArdvarkErick It also co-locates queryKey and queryFn and will thus make getQueryData and setQueryData type-safe. Lately, I'm recommending to start with queryOptions abstractions and inline actual useQuery calls in the component. It works really well.

Tanstack Query pattern: 1. Colocate related queries and mutations 2. Centralize queryKeys If a query sets a key, and a mutation invalidates the same key, they probably belong in the same file. Example: This contains related queries and mutations and centralizes queryKeys.

Source code in github.com/Newbie012/pg-q…

Playground in pg-query-ast-explorer.vercel.app

PG Query AST Explorer is now live

@TkDodo By the time it reaches stage 4... 😅

@CoEliya do expressions ftw 🙌

I was a bit vague, so here is a better example. There's an obvious bug in here: When you're pending, you also have no data, so you'll render the empty screen right away with the spinner. The condition needs to be !data && !isPending. Gross. Also, all conditions we add in the future must check each branch. I've seen those components evolve into huge monsters a lot, but also this rather simple flow is already hard to grasp. It's not clear to me what actually gets rendered in each "state". Cognitive load is what matters (great read btw: github.com/zakirullin/cog…) So why did we add those conditions in the first place? Well, because they all share the div and the Heading and the Card with the same styles. If that becomes it's own layout component, things will be much easier to read, because we can then use early returns: We mostly don't care about the layouting jsx, it's boilerplate, so move it away from the logic. This version doesn't have the bug. Also notice how TypeScript now helps us with type inference. Because we have returned with !data, it now knows that data is defined afterwards. If it's easier to grap for the compiler (which is pretty smart), it's surely also easier for humans to understand.