Yiming Cao

Btw, you can use this method to see he pre-compiled policies in TS form. ```prisma plugin policy { provider = '@core/access-policy' preserveTsFiles = true ``` After running `zenstack generate`, you...

Hi @vgarmash , thanks for reporting this. I understand it feels redundant, but currently ZenStack's RESTful API follows the JSON:API specification: https://jsonapi.org/format/#crud-updating. The "id" field in the payload is required.

Hi @Azzerty23 , thanks for the comment and example. My apologies for not being clear in the initial draft. The plugins are supposed to be implemented outside of ZenStack, and...

Thanks for the pointer @bvkimball ! I didn't know Supabase has a set of Postgres FDW. They can be very good references. Yes, indeed the idea is quite close to...

> Very interesting. I just wonder if defining the plugins on the schema itself would later become a limitation in terms of adding custom logic to the plugin functions /...

> One question I do have: > > Let’s say I plan to use Lemonsqueezy as a payments/billing service instead of Stripe, and the Zenstack library doesn’t have a first-party...

A design challenge is how to provide the flexibility to allow permission checking given different granularity of conditions, from the weakest one (only giving model type and CRUD operation), to...

> @ymc9 adding some questions here: > > > > 1. Would the approach to implement this require more database calls or can these all be done at runtime? Ideally,...

> Hi @ymc9, I'm interested in working on it. How do you envision the design? Initially, I was wondering if it might be better to create a single generic hook...

Implemented in 2.1.0