zenstackhq / zenstack Goto Github PK

One-to-one relation requires one side of reference to be marked @unique. It's not checked today.

repro:

model User {
    id String @id @default(cuid())
    data UserData?
}

model UserData {
    id String @id @default(cuid())
    user User  @relation(fields: [userId], references: [id])
    userId String
}

Error:
Error parsing attribute "@relation": A one-to-one relation must use unique fields on the defining side. Either add an @unique attribute to the field userId, or change the relation to one-to-many.

Arguments of get/find hooks can come from other hooks and may not be available when a component is first rendered. We should probably provide a way to "mute" the hooks until args are ready.

Describe the bug
VS Code extension occasionally reports errors with a stack like:

An error occurred during validation: Error: AST node has no document.
at Mb (/Users/yiming/.vscode/extensions/zenstack.zenstack-1.0.4/bundle/language-server/main.js:36:5802)
at get ref [as ref] (/Users/yiming/.vscode/extensions/zenstack.zenstack-1.0.4/bundle/language-server/main.js:3736:24701)
at rM (/Users/yiming/.vscode/extensions/zenstack.zenstack-1.0.4/bundle/language-server/main.js:6630:26281)
at tc.validate (/Users/yiming/.vscode/extensions/zenstack.zenstack-1.0.4/bundle/language-server/main.js:6630:32491)
at ch.checkExpression (/Users/yiming/.vscode/extensions/zenstack.zenstack-1.0.4/bundle/language-server/main.js:6630:33668)
at /Users/yiming/.vscode/extensions/zenstack.zenstack-1.0.4/bundle/language-server/main.js:3736:29142
at /Users/yiming/.vscode/extensions/zenstack.zenstack-1.0.4/bundle/language-server/main.js:3582:26330
at async Promise.all (index 8)
at async eg.validateAst (/Users/yiming/.vscode/extensions/zenstack.zenstack-1.0.4/bundle/language-server/main.js:3582:26175)
at async eg.validateDocument (/Users/yiming/.vscode/extensions/zenstack.zenstack-1.0.4/bundle/language-server/main.js:3582:25876)

To Reproduce
Can't reproduce consistently.

Expected behavior
No error.

Environment (please complete the following information):

• OS: Mac OS
• Node version: 16.15
• NPM version: 8.9.2
• Database type: Sqlite

If a model doesn't have any policy, by default, no operation is permitted, so no hooks are generated. However, this can be confusing to new users. We should issue a warning during generation.

enum OrderStatus {
  UNPAID
  PAID
}

model Order {
  id String @default(cuid())
  status OrderStatus(UNPAID)
}

Error: Value is not assignable to parameter

node_modules/.zenstack/src/auth/authorize.ts:32:21 - error TS2322: Type '{ id: true; email: true; password: true; name: true; }' is not assignable to type 'UserSelect'.
Object literal may only specify known properties, and 'name' does not exist in type 'UserSelect'.

32 name: true,

It's generated as "PUT" now but should be "POST" instead.

Currently, result type of auth() function is weakly resolved because it needs to refer to the User model defined by user. We should actually let it resolve to the user-defined User model.

error: Unknown escape sequence. If the value is a windows-style path, \ must be escaped as \\.
--> schema.prisma:8
|
7 | provider = "prisma-client-js"
8 | output = "..\node_modules.zenstack.prisma"

Right now it's only allowed for model and model field.

Should give an HTTP 4xx with an appropriate error instead.

Right now, the project implicitly signup a user account if it's not found during signup. We should change it to explicit signup as a better sample.

Right now, all logging is done with console. We need to have an appropriate mechanism for it.

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:
1.
2.
3.

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

• OS: [e.g. Mac OS 13.0]
• Node version: [e.g. 16.15.0]
• NPM version: [e.g. 8.19.2]
• Database type: [e.g. Postgresql]

Additional context
Add any other context about the problem here.

When a read request is reject, log message is incorrect:

GET Post: Request handler error: DENIED_BY_POLICY, the request was denied due to access policy violation: denied by policy before update: entities failed 'read' check, User#[cla8yyvto0001vh8hy4cxeura]

Previously access policies are tested at REST API level. Should migrate it to runtime API level and make it independent to transport.

Describe the bug

model Model {
        id String @id @default(uuid())
        a String
        b String
        @@unique([a, b])
        @@allow('all', true)
}

await withPresets(prisma).model.findUnique({ where: { a_b: { a: 'a', b: 'b' } } }));

Error

Invalid prisma.model.findMany() invocation:

{
  where: {
    AND: [
      {
        a_b: {
        ~~~
          a: 'a1',
          b: 'b1'
        }
      },
      {
        x: {
          gt: 0
        }
      }
    ]
  }
}