Skip to content

Conversation

@ymc9
Copy link
Member

@ymc9 ymc9 commented Jul 9, 2024

Summary by CodeRabbit

  • New Features

    • Introduced the check() function in the Z-Model language to verify operation permissions on a field.
    • Added a new section on delegating access control in ZenStack to maintain DRY access policies.
    • Enhanced the ZenStackModuleOptions interface in NestJS with an optional model parameter.
  • Documentation

    • Updated sidebar labels from "Sample Catalog" to "Sample Projects."
    • Added the findMany method to the list of "read" operation types.
    • Updated a link from "Sample Catalog" to "Samples" in the "Other Resources" section.
    • Introduced the concept of delegating access control to related models in ZenStack's access policies.

@vercel
Copy link

vercel bot commented Jul 9, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
zenstack-new-site ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 12, 2024 4:45pm

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 9, 2024

Walkthrough

The update enhances the ZenStack framework by introducing a new check() function for verifying user permissions on field operations, updates sidebar labels and links for better navigation, and adds new sections on access policy delegation and keeping policies DRY in the documentation. Additionally, the ZenStackModuleOptions interface in the NestJS server adapter has been updated to include an optional model parameter.

Changes

File Path Change Summary
docs/reference/zmodel-language.md Added a new check() function in the Z-Model language for permission verification.
docs/samples.md Updated sidebar label from "Sample Catalog" to "Sample Projects".
docs/the-complete-guide/part1/4-access-policy/4.1-model-level.md Added findMany method to list of methods under the "read" operation type.
docs/the-complete-guide/part1/4-access-policy/4.8-delegate-to-relation.md Introduced concept of delegating access control to related models to maintain a declarative authorization model.
docs/welcome.md Updated link from "Sample Catalog" to "Samples" in the "Other Resources" section.
docs/the-complete-guide/part1/4-access-policy/4.8-keep-policies-dry.md Added new section on keeping access policies DRY by delegating access control to related models.
docs/reference/server-adapters/nestjs.mdx Updated ZenStackModuleOptions interface to include an optional model parameter.

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between a8b80fb and 4147ea9.

Files selected for processing (1)
  • docs/reference/server-adapters/nestjs.mdx (1 hunks)

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
Tips

Chat

There are 3 ways to chat with CodeRabbit:

‼️ IMPORTANT
Auto-reply has been disabled for this repository in the CodeRabbit settings. 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.
    • @coderabbitai help me debug CodeRabbit configuration file.

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 an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 13


> One has full access to a `Todo` entity if he can read its parent `List` entity.
ZenStack provides a `check()` attribute function for you to delegate access control of the current model to a relation. Let's refactor the `Todo` model to use this feature 🛠️:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add hyphen to "To-do".

It appears that a hyphen is missing in the noun "To-do".

- Let's refactor the `Todo` model to use this feature 🛠️:
+ Let's refactor the `To-do` model to use this feature 🛠️:
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
ZenStack provides a `check()` attribute function for you to delegate access control of the current model to a relation. Let's refactor the `Todo` model to use this feature 🛠️:
ZenStack provides a `check()` attribute function for you to delegate access control of the current model to a relation. Let's refactor the `To-do` model to use this feature 🛠️:
Tools
LanguageTool

[grammar] ~52-~52: It appears that a hyphen is missing in the noun “To-do” (= task) or did you mean the verb “to do”?
Context: ...model to a relation. Let's refactor the Todo model to use this feature 🛠️: ```zmo...

(TO_DO_HYPHEN)

}
```

When authorizing an operation on a `Todo` (e.g., "update"), ZenStack will make the decision based on if the related `List` entity is readable. If you adjust the rules on `List` in the future, the `Todo` model automatically follows without needing any changes.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fix heading level increment.

Expected: h2; Actual: h3. Heading levels should only increment by one level at a time.

- ### Parent-Child Duplication
+ ## Parent-Child Duplication
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
When authorizing an operation on a `Todo` (e.g., "update"), ZenStack will make the decision based on if the related `List` entity is readable. If you adjust the rules on `List` in the future, the `Todo` model automatically follows without needing any changes.
## Parent-Child Duplication
Tools
LanguageTool

[grammar] ~63-~63: It appears that a hyphen is missing in the noun “To-do” (= task) or did you mean the verb “to do”?
Context: ...``` When authorizing an operation on a Todo (e.g., "update"), ZenStack will make t...

(TO_DO_HYPHEN)


[grammar] ~63-~63: It appears that a hyphen is missing in the noun “To-do” (= task) or did you mean the verb “to do”?
Context: ... the rules on List in the future, the Todo model automatically follows without ne...

(TO_DO_HYPHEN)


Add hyphen to "To-do".

It appears that a hyphen is missing in the noun "To-do".

- When authorizing an operation on a `Todo` (e.g., "update"), ZenStack will make the decision based on if the related `List` entity is readable.
+ When authorizing an operation on a `To-do` (e.g., "update"), ZenStack will make the decision based on if the related `List` entity is readable.
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
When authorizing an operation on a `Todo` (e.g., "update"), ZenStack will make the decision based on if the related `List` entity is readable. If you adjust the rules on `List` in the future, the `Todo` model automatically follows without needing any changes.
When authorizing an operation on a `To-do` (e.g., "update"), ZenStack will make the decision based on if the related `List` entity is readable. If you adjust the rules on `List` in the future, the `Todo` model automatically follows without needing any changes.
Tools
LanguageTool

[grammar] ~63-~63: It appears that a hyphen is missing in the noun “To-do” (= task) or did you mean the verb “to do”?
Context: ...``` When authorizing an operation on a Todo (e.g., "update"), ZenStack will make t...

(TO_DO_HYPHEN)


[grammar] ~63-~63: It appears that a hyphen is missing in the noun “To-do” (= task) or did you mean the verb “to do”?
Context: ... the rules on List in the future, the Todo model automatically follows without ne...

(TO_DO_HYPHEN)

@@ -0,0 +1,65 @@
---
sidebar_label: 4.8 Delegating Access Control To Relations
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fix the sidebar label for consistency.

The sidebar label should start with a capital letter for consistency.

- sidebar_label: 4.8 Delegating Access Control To Relations
+ sidebar_label: 4.8 Delegating Access Control to Relations
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
sidebar_label: 4.8 Delegating Access Control To Relations
sidebar_label: 4.8 Delegating Access Control to Relations

}
```

Although not a 100% match, the rules of `Todo` closely resemble those of `List`. How can we avoid such duplication and stay DRY?
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add hyphen to "To-do".

It appears that a hyphen is missing in the noun "To-do".

- Although not a 100% match, the rules of `Todo` closely resemble those of `List`. How can we avoid such duplication and stay DRY?
+ Although not a 100% match, the rules of `To-do` closely resemble those of `List`. How can we avoid such duplication and stay DRY?
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
Although not a 100% match, the rules of `Todo` closely resemble those of `List`. How can we avoid such duplication and stay DRY?
Although not a 100% match, the rules of `To-do` closely resemble those of `List`. How can we avoid such duplication and stay DRY?
Tools
LanguageTool

[grammar] ~44-~44: It appears that a hyphen is missing in the noun “To-do” (= task) or did you mean the verb “to do”?
Context: ...Although not a 100% match, the rules of Todo closely resemble those of List. How ...

(TO_DO_HYPHEN)


### Parent-Child Duplication

If your application has a hierarchy of models, you'll quite often notice that the child models repeat the access policies of their parent. This can be found in our Todo schema, where `List` and `Todo` models have a parent-child relationship:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add hyphen to "To-do".

It appears that a hyphen is missing in the noun "To-do".

- This can be found in our Todo schema, where `List` and `Todo` models have a parent-child relationship:
+ This can be found in our To-do schema, where `List` and `To-do` models have a parent-child relationship:
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
If your application has a hierarchy of models, you'll quite often notice that the child models repeat the access policies of their parent. This can be found in our Todo schema, where `List` and `Todo` models have a parent-child relationship:
If your application has a hierarchy of models, you'll quite often notice that the child models repeat the access policies of their parent. This can be found in our To-do schema, where `List` and `To-do` models have a parent-child relationship:
Tools
LanguageTool

[grammar] ~12-~12: It appears that a hyphen is missing in the noun “To-do” (= task) or did you mean the verb “to do”?
Context: ... their parent. This can be found in our Todo schema, where List and Todo models ...

(TO_DO_HYPHEN)


[grammar] ~12-~12: It appears that a hyphen is missing in the noun “To-do” (= task) or did you mean the verb “to do”?
Context: ...nd in our Todo schema, where List and Todo models have a parent-child relationshi...

(TO_DO_HYPHEN)


Checks if the current user can perform the given operation on the given field.

_Params_
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fix emphasis used instead of a heading.

Emphasis used instead of a heading.

- _Params_
+ ### Params

Also applies to: 930-930

Tools
Markdownlint

925-925: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

_Params_

- `field`: The field to check access for. Must be a relation field.
- `operation`: The operation to check access for. Can be "read", "create", "update", or "delete". If the operation is not provided, it defaults the operation of the containing policy rule.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fix punctuation for readability.

A punctuation mark might be missing here.

- -  `operation`: The operation to check access for. Can be "read", "create", "update", or "delete".
+ -  `operation`: The operation to check access for. Can be "read", "create", "update", or "delete".

Committable suggestion was skipped due to low confidence.

Tools
LanguageTool

[uncategorized] ~928-~928: Loose punctuation mark.
Context: ...Must be a relation field. - operation: The operation to check access for. Can ...

(UNLIKELY_OPENING_PUNCTUATION)


[style] ~928-~928: To form a complete sentence, be sure to include a subject.
Context: ...on`: The operation to check access for. Can be "read", "create", "update", or "dele...

(MISSING_IT_THERE)


Fix incomplete sentence.

To form a complete sentence, be sure to include a subject.

- Can be "read", "create", "update", or "delete".
+ The operation can be "read", "create", "update", or "delete".
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- `operation`: The operation to check access for. Can be "read", "create", "update", or "delete". If the operation is not provided, it defaults the operation of the containing policy rule.
`operation`: The operation to check access for. The operation can be "read", "create", "update", or "delete". If the operation is not provided, it defaults the operation of the containing policy rule.
Tools
LanguageTool

[uncategorized] ~928-~928: Loose punctuation mark.
Context: ...Must be a relation field. - operation: The operation to check access for. Can ...

(UNLIKELY_OPENING_PUNCTUATION)


[style] ~928-~928: To form a complete sentence, be sure to include a subject.
Context: ...on`: The operation to check access for. Can be "read", "create", "update", or "dele...

(MISSING_IT_THERE)

function future(): Any {}
```

Gets the "post-update" state of an entity. Only valid when used in a "update" access policy. Read more about access policies [here](#access-policy).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fix grammatical error: Use "an" instead of "a".

Use “an” instead of ‘a’ if the following word starts with a vowel sound.

- Only valid when used in a "update" access policy.
+ Only valid when used in an "update" access policy.
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
Gets the "post-update" state of an entity. Only valid when used in a "update" access policy. Read more about access policies [here](#access-policy).
Gets the "post-update" state of an entity. Only valid when used in an "update" access policy. Read more about access policies [here](#access-policy).
Tools
LanguageTool

[misspelling] ~915-~915: Use “an” instead of ‘a’ if the following word starts with a vowel sound, e.g. ‘an article’, ‘an hour’.
Context: ...e of an entity. Only valid when used in a "update" access policy. Read more about...

(EN_A_VS_AN)

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Outside diff range and nitpick comments (15)
docs/the-complete-guide/part1/4-access-policy/4.8-keep-policies-dry.md (9)

8-8: Fix grammatical error: Use "an" instead of "a".

Use “an” instead of ‘a’ if the following word starts with a vowel sound.

- in a intuitive and declarative way
+ in an intuitive and declarative way
Tools
LanguageTool

[misspelling] ~8-~8: Use “an” instead of ‘a’ if the following word starts with a vowel sound, e.g. ‘an article’, ‘an hour’.
Context: ...powerful tool to model authorization in a intuitive and declarative way. However,...

(EN_A_VS_AN)


12-12: Fix grammatical error: Use hyphen for "To-do".

It appears that a hyphen is missing in the noun “To-do” (= task) or did you mean the verb “to do”?

- in our Todo schema
+ in our To-do schema
Tools
LanguageTool

[grammar] ~12-~12: It appears that a hyphen is missing in the noun “To-do” (= task) or did you mean the verb “to do”?
Context: ... their parent. This can be found in our Todo schema, where List and Todo models ...

(TO_DO_HYPHEN)


[grammar] ~12-~12: It appears that a hyphen is missing in the noun “To-do” (= task) or did you mean the verb “to do”?
Context: ...nd in our Todo schema, where List and Todo models have a parent-child relationshi...

(TO_DO_HYPHEN)


44-44: Fix grammatical error: Use hyphen for "To-do".

It appears that a hyphen is missing in the noun “To-do” (= task) or did you mean the verb “to do”?

- the rules of `Todo` closely resemble
+ the rules of `To-do` closely resemble
Tools
LanguageTool

[grammar] ~44-~44: It appears that a hyphen is missing in the noun “To-do” (= task) or did you mean the verb “to do”?
Context: ...Although not a 100% match, the rules of Todo closely resemble those of List. How ...

(TO_DO_HYPHEN)


48-48: Fix grammatical error: Use hyphen for "To-do".

It appears that a hyphen is missing in the noun “To-do” (= task) or did you mean the verb “to do”?

- the rules of `Todo` can summarized
+ the rules of `To-do` can be summarized
Tools
LanguageTool

[grammar] ~48-~48: It appears that a hyphen is missing in the noun “To-do” (= task) or did you mean the verb “to do”?
Context: ...t the policies, we'll find the rules of Todo can summarized into a single statement...

(TO_DO_HYPHEN)


[grammar] ~48-~48: The modal verb ‘can’ requires the verb’s base form.
Context: ...ies, we'll find the rules of Todo can summarized into a single statement: > One has ful...

(MD_BASEFORM)


50-50: Fix grammatical error: Use hyphen for "To-do".

It appears that a hyphen is missing in the noun “To-do” (= task) or did you mean the verb “to do”?

- access to a `Todo` entity
+ access to a `To-do` entity
Tools
LanguageTool

[grammar] ~50-~50: It appears that a hyphen is missing in the noun “To-do” (= task) or did you mean the verb “to do”?
Context: ... statement: > One has full access to a Todo entity if he can read its parent `List...

(TO_DO_HYPHEN)


52-52: Fix grammatical error: Use hyphen for "To-do".

It appears that a hyphen is missing in the noun “To-do” (= task) or did you mean the verb “to do”?

- refactor the `Todo` model
+ refactor the `To-do` model
Tools
LanguageTool

[grammar] ~52-~52: It appears that a hyphen is missing in the noun “To-do” (= task) or did you mean the verb “to do”?
Context: ...model to a relation. Let's refactor the Todo model to use this feature 🛠️: ```zmo...

(TO_DO_HYPHEN)


63-63: Fix grammatical error: Use hyphen for "To-do".

It appears that a hyphen is missing in the noun “To-do” (= task) or did you mean the verb “to do”?

- an operation on a `Todo`
+ an operation on a `To-do`
Tools
LanguageTool

[grammar] ~63-~63: It appears that a hyphen is missing in the noun “To-do” (= task) or did you mean the verb “to do”?
Context: ...``` When authorizing an operation on a Todo (e.g., "update"), ZenStack will make t...

(TO_DO_HYPHEN)


[grammar] ~63-~63: It appears that a hyphen is missing in the noun “To-do” (= task) or did you mean the verb “to do”?
Context: ... the rules on List in the future, the Todo model automatically follows without ne...

(TO_DO_HYPHEN)


63-63: Fix grammatical error: Use hyphen for "To-do".

It appears that a hyphen is missing in the noun “To-do” (= task) or did you mean the verb “to do”?

- the `Todo` model automatically follows
+ the `To-do` model automatically follows
Tools
LanguageTool

[grammar] ~63-~63: It appears that a hyphen is missing in the noun “To-do” (= task) or did you mean the verb “to do”?
Context: ...``` When authorizing an operation on a Todo (e.g., "update"), ZenStack will make t...

(TO_DO_HYPHEN)


[grammar] ~63-~63: It appears that a hyphen is missing in the noun “To-do” (= task) or did you mean the verb “to do”?
Context: ... the rules on List in the future, the Todo model automatically follows without ne...

(TO_DO_HYPHEN)


10-10: Fix heading level.

Heading levels should only increment by one level at a time.

- ### Parent-Child Duplication
+ ## Parent-Child Duplication
Tools
Markdownlint

10-10: Expected: h2; Actual: h3
Heading levels should only increment by one level at a time

(MD001, heading-increment)

docs/reference/zmodel-language.md (6)

915-915: Fix grammatical error: Use "an" instead of "a".

Use “an” instead of ‘a’ if the following word starts with a vowel sound.

- used in a "update" access policy
+ used in an "update" access policy
Tools
LanguageTool

[misspelling] ~915-~915: Use “an” instead of ‘a’ if the following word starts with a vowel sound, e.g. ‘an article’, ‘an hour’.
Context: ...e of an entity. Only valid when used in a "update" access policy. Read more about...

(EN_A_VS_AN)


927-927: Fix punctuation for readability.

A punctuation mark might be missing here.

- Must be a relation field.
+ Must be a relation field.
Tools
LanguageTool

[uncategorized] ~927-~927: Loose punctuation mark.
Context: ...n the given field. Params - field: The field to check access for. Must be ...

(UNLIKELY_OPENING_PUNCTUATION)


928-928: Fix incomplete sentence.

To form a complete sentence, be sure to include a subject.

- Can be "read", "create", "update", or "delete".
+ The operation can be "read", "create", "update", or "delete".
Tools
LanguageTool

[uncategorized] ~928-~928: Loose punctuation mark.
Context: ...Must be a relation field. - operation: The operation to check access for. Can ...

(UNLIKELY_OPENING_PUNCTUATION)


[style] ~928-~928: To form a complete sentence, be sure to include a subject.
Context: ...on`: The operation to check access for. Can be "read", "create", "update", or "dele...

(MISSING_IT_THERE)


[uncategorized] ~928-~928: Possible missing preposition found.
Context: ... operation is not provided, it defaults the operation of the containing policy rule...

(AI_HYDRA_LEO_MISSING_TO)


928-928: Fix punctuation for readability.

A punctuation mark might be missing here.

- it defaults the operation of the containing policy rule.
+ it defaults to the operation of the containing policy rule.
Tools
LanguageTool

[uncategorized] ~928-~928: Loose punctuation mark.
Context: ...Must be a relation field. - operation: The operation to check access for. Can ...

(UNLIKELY_OPENING_PUNCTUATION)


[style] ~928-~928: To form a complete sentence, be sure to include a subject.
Context: ...on`: The operation to check access for. Can be "read", "create", "update", or "dele...

(MISSING_IT_THERE)


[uncategorized] ~928-~928: Possible missing preposition found.
Context: ... operation is not provided, it defaults the operation of the containing policy rule...

(AI_HYDRA_LEO_MISSING_TO)


925-925: Fix emphasis used instead of a heading.

Emphasis used instead of a heading.

- _Params_
+ ### Params
Tools
Markdownlint

925-925: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)


930-930: Fix emphasis used instead of a heading.

Emphasis used instead of a heading.

- _Example_
+ ### Example
Tools
Markdownlint

930-930: null
Emphasis used instead of a heading

(MD036, no-emphasis-as-heading)

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Outside diff range, codebase verification and nitpick comments (1)
docs/reference/server-adapters/nestjs.mdx (1)

121-121: Document the purpose of the new model parameter.

The new model parameter is added to the getEnhancedPrisma callback function. Ensure to document its purpose and usage to maintain clarity.

- getEnhancedPrisma: (model?: string | symbol) => unknown;
+ /**
+  * A callback for getting an enhanced `PrismaClient`.
+  * @param model - An optional parameter specifying the model to be used.
+  */
+ getEnhancedPrisma: (model?: string | symbol) => unknown;

@ymc9 ymc9 merged commit f3333a7 into main Jul 12, 2024
@ymc9 ymc9 deleted the docs/release-2.3.0 branch July 12, 2024 17:18
@coderabbitai coderabbitai bot mentioned this pull request Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants