fix: enhancer generation issue with auth model with ignored fields

[ymc9]

Summary by CodeRabbit

• New Features

  • Enhanced type generation in the ZenStack Language Tools to improve user and profile data handling.

• Chores

  • Updated various packages to version "2.0.0-beta.14" to ensure compatibility and stability across the platform.

[coderabbitai]

Walkthrough

Walkthrough

This update primarily involves incrementing the version number from "2.0.0-beta.13" to "2.0.0-beta.14" across various packages within the project. Additionally, enhancements include the introduction of new checks and modifications in the schema generation logic, specifically in the handling of user and profile types.

Changes

Files	Change Summary
package.json, .../ide/jetbrains/package.json, .../language/package.json, .../misc/redwood/package.json, .../plugins/.../package.json, .../runtime/package.json, .../schema/package.json, .../sdk/package.json, .../server/package.json, .../testtools/package.json	Updated version from "2.0.0-beta.13" to "2.0.0-beta.14"
.../ide/jetbrains/build.gradle.kts	Updated version from "2.0.0-beta.13" to "2.0.0-beta.14" for JetBrains IDE plugin
.../schema/src/plugins/enhancer/auth-type-generator.ts	Added imports, conditional checks, and modified type generation

Possibly related issues

• Issue [Feature Request] Automatically do a database fetch if the policy rules use fields not provided in the user context object #820: The enhancements made to auth-type-generator.ts might address issues related to handling auth() expressions and ensuring proper field availability in user contexts, as it involves modifications to type generation and field handling logic.
• Issue Delegating models can't use @@map() #1167: Although this PR does not directly address the specific delegation and @@map() issues mentioned, the enhancements in schema generation could indirectly affect how these configurations are handled in future updates.

---

Recent Review Details

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 7960595 and 269d4a7.

Files selected for processing (15)

• package.json (1 hunks)
• packages/ide/jetbrains/build.gradle.kts (1 hunks)
• packages/ide/jetbrains/package.json (1 hunks)
• packages/language/package.json (1 hunks)
• packages/misc/redwood/package.json (1 hunks)
• packages/plugins/openapi/package.json (1 hunks)
• packages/plugins/swr/package.json (1 hunks)
• packages/plugins/tanstack-query/package.json (1 hunks)
• packages/plugins/trpc/package.json (1 hunks)
• packages/runtime/package.json (1 hunks)
• packages/schema/package.json (1 hunks)
• packages/schema/src/plugins/enhancer/enhance/auth-type-generator.ts (6 hunks)
• packages/sdk/package.json (1 hunks)
• packages/server/package.json (1 hunks)
• packages/testtools/package.json (1 hunks)

Files skipped from review due to trivial changes (8)

• package.json
• packages/ide/jetbrains/package.json
• packages/language/package.json
• packages/misc/redwood/package.json
• packages/plugins/openapi/package.json
• packages/runtime/package.json
• packages/schema/package.json
• packages/server/package.json

Additional comments not posted (9)

packages/testtools/package.json (1)

3-3: Version update from "2.0.0-beta.13" to "2.0.0-beta.14" is correct and aligns with the PR objectives.

packages/plugins/trpc/package.json (1)

4-4: Version update from "2.0.0-beta.13" to "2.0.0-beta.14" is correct and aligns with the PR objectives.

packages/sdk/package.json (1)

3-3: Version update from "2.0.0-beta.13" to "2.0.0-beta.14" is correct and aligns with the PR objectives.

packages/plugins/swr/package.json (1)

4-4: Version update from "2.0.0-beta.13" to "2.0.0-beta.14" is correct and aligns with the PR objectives.

packages/ide/jetbrains/build.gradle.kts (1)

12-12: Version update from "2.0.0-beta.13" to "2.0.0-beta.14" is correct and aligns with the PR objectives.

packages/plugins/tanstack-query/package.json (1)

4-4: Version update from "2.0.0-beta.13" to "2.0.0-beta.14" is correct and aligns with the PR objectives.

packages/schema/src/plugins/enhancer/enhance/auth-type-generator.ts (3)

76-78: Ensure that the isIgnoredField function is correctly checking the field's attributes before adding it to pickFields. This logic prevents ignored fields from being processed, aligning with the PR objectives.

---

92-95: The conditional check in addPickField for scalar fields is correctly implemented to respect the isIgnoredField status. This is crucial for maintaining data integrity by not processing ignored fields.

---

113-121: > 📝 NOTE

This review was outside the diff hunks and was mapped to the diff hunk with the greatest overlap. Original lines [104-118]

The type generation for User and Profile includes Record<string, unknown> to handle additional properties dynamically. This is a robust approach for extending types with potential future properties.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

Note: Auto-reply has been disabled for this repository by the repository owner. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.