-
-
Notifications
You must be signed in to change notification settings - Fork 113
fix(delegate): update @updatedAt
fields inherited from delegate bases automatically
#2119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…es automatically fixes #2101
📝 Walkthrough""" WalkthroughThe changes implement logic to ensure that when updating fields of extended (delegate) models, any inherited Changes
Sequence Diagram(s)sequenceDiagram
participant Client
participant DelegateProxyHandler
participant Model
participant BaseModel
Client->>DelegateProxyHandler: Update extended model record
DelegateProxyHandler->>BaseModel: Identify inherited @updatedAt fields
DelegateProxyHandler->>Model: Inject current date into inherited @updatedAt fields
DelegateProxyHandler->>Model: Process update payload and perform update
Model-->>Client: Return updated record
Assessment against linked issues
Note ⚡️ AI Code Reviews for VS Code, Cursor, WindsurfCodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback. Note ⚡️ Faster reviews with cachingCodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure ✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. 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 using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this 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
🧹 Nitpick comments (1)
tests/integration/tests/enhancements/with-delegate/plugin-interaction.test.ts (1)
59-151
: Consider adding tests specifically for @updatedAt behaviorWhile the existing changes ensure the schemas include
updatedAt
fields, consider adding tests that specifically verify the automatic updating behavior of@updatedAt
fields inherited from delegate bases. For example, a test that performs an update operation and then verifies theupdatedAt
timestamp has changed would directly validate the fix for issue #2101.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting
📒 Files selected for processing (1)
tests/integration/tests/enhancements/with-delegate/plugin-interaction.test.ts
(4 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (6)
- GitHub Check: dependency-review
- GitHub Check: build-test (20.x)
- GitHub Check: Analyze (javascript-typescript)
- GitHub Check: OSSAR-Scan
- GitHub Check: build-test (20.x)
- GitHub Check: build-test (20.x)
🔇 Additional comments (4)
tests/integration/tests/enhancements/with-delegate/plugin-interaction.test.ts (4)
68-68
: LGTM: Added updatedAt field to support automatic timestamp updatesThe addition of the
updatedAt
field correctly supports testing the fix for issue #2101, ensuring that objects conform to the updated schema where@updatedAt
fields are inherited from delegate bases.
78-78
: LGTM: Added updatedAt field for consistent schema validationThe
updatedAt
field has been appropriately added to this test case, maintaining consistency with the schema changes.
92-92
: LGTM: Properly included updatedAt in Video schema validationThis change correctly adds the
updatedAt
field to the Video object being validated, supporting the testing of inherited@updatedAt
fields from the Asset base model.
104-104
: LGTM: Added updatedAt to negative test caseThe
updatedAt
field has been appropriately added to this negative test case, ensuring the test validates field requirements correctly while supporting the@updatedAt
functionality.
fixes #2101