A Principled Approach to Querying Data – A Type-Safe Search DSL(claudiu-ivan.com) |
A Principled Approach to Querying Data – A Type-Safe Search DSL(claudiu-ivan.com) |
Do they? I think users are amazed if anything works without internet with modern applications.
Failover is hard, and there generally aren't hard rules for what to do if data isn't available or how to communicate to a user in a specific offline situation on how the current state of an offline app affects what they see -- and even when they would care or what they could do about it when they do care
Check it out here: https://github.com/williamcotton/search-input-query
There's an animated GIF of the demo so you can get a very quick idea of how it works!
For a more database specific, type-safe, data querying solution, I like to use https://kysely.dev
I found out about stackzen yesterday, really like the RBAC/ABAC backed up into the models/codegen stuff, been thinking about just using that for our custom logic and maybe add RLS pg a la supabase but also codegen from the same .zmodel from zenstack model that generates prisma models/migrations have it generate RLS sql migrations code
thoughts??
also maybe postgres views to handle field/attribute level security since rows is mostly about whole columns
main goal is to secure the data at all the levels of the stack from db to api to app so there's no footguns in the future where someone with a pg user or modifying our clients can see data they shouldn't etc
RLS is hard to work with, hard to debug, hard to reason about, cumbersome. It is however powerful.
so my mind went to leverage the .zmodel to generate not only the prisma schemas through it and the client api codegen sdk, but also the RLS stuff either with plain sql migrations or a specific framework for rls.
all in all this is probably too much and as long as the app-api level is secure with zenstack and i dont use pg directly anywhere else it should be 'safe' i just wanted to harden all the stack speaking of sorts... idk