-
-
Notifications
You must be signed in to change notification settings - Fork 132
feat: fields argument for @updatedAt
#2379
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
Open
sanny-io
wants to merge
8
commits into
zenstackhq:dev
Choose a base branch
from
sanny-io:feat/updated-at-fields
base: dev
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
b44df85
feat: `fields` argument for `@updatedAt`
sanny-io 02015fa
chore: add tests
sanny-io 4bcbb13
chore: remove old tests
sanny-io 3c87470
chore: update e2e schema
sanny-io 2bea83b
Address AI comments.
sanny-io 23a2dda
Trigger Build
sanny-io a3c2d22
Merge branch 'dev' into feat/updated-at-fields
sanny-io d3b5032
fix: handle relations
sanny-io File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Don't treat every owned relation payload as an FK change.
Line 1540 expands any owned relation key to
[relation, ...relation.fields], so Line 1176 will also match@updatedAt(fields: [userId])for a payload likedata: { title: 'x', user: { update: { name: 'y' } } }. That only mutates the related row, but thetitlewrite gives the parent row a real update so the timestamp bump gets persisted anyway. Please derive the effective fields from operations that actually produceparentUpdates/owned-FK writes, or move this decision after relation processing. A regression test for nested relationupdateand the matched-upsertpath would lock this down.Also applies to: 1540-1554
🤖 Prompt for AI Agents