Dejan Mircevski

The instructions will vary with the version. An upgrade may require rewriting some client code, new policy language, or running a provided one-time script. `npx` is only relevant to the...

For the record: #1522 made this less of a problem.

Please provide instructions to reproduce. We can't do anything with this until we have the endpoints and models code.

@7flash please paste text instead of screenshots, it's much more useful. This particular pic is cropped, missing a part of that warning. I believe these warnings aren't bringing `chiseld` down,...

If you absolutely require separate databases, then 2. is your only option right now. But if you trust ChiselStrike to keep the users out of each other's data, consider using...

> match_login seems a good option.. but also I need to implement "sharing" feature.. how can I modify it's transformer to NOT ignore those rows which has been made public...

This is documented in the [adapter README](https://github.com/nextauthjs/next-auth/pull/4573/files#diff-d27bf1a87c66eb6d67fd815eccec4c04aa7d0be13a085610dada8ff30df53d10). When that's committed to NextAuth, we'll link to it from our doc.

> but what if I want to use it without NextAuth? We currently [only support](https://docs.chiselstrike.com/InDepth/login) leveraging NextAuth to populate AuthUser. We had to make a choice; we don't want to...

> hi @dekimir, I see that this PR hasn't been touched recently, do you think you can pick up the pieces and get this in soon? Sorry, I'm unable to...

> We want to express "ck > (a, *) and ck < (b, c)" where * means null. @tgrabiec Isn't that already possible? ```cql cqlsh:ks> CREATE TABLE t2 ( p...