fix: exclude emailAccountId from nested action createMany#2169
Open
gentlemandev wants to merge 1 commit intomainfrom
Open
fix: exclude emailAccountId from nested action createMany#2169gentlemandev wants to merge 1 commit intomainfrom
gentlemandev wants to merge 1 commit intomainfrom
Conversation
Prisma auto-fills emailAccountId via the compound FK [ruleId, emailAccountId] when using nested createMany under Rule. Passing it explicitly causes "Unknown argument emailAccountId" at runtime, even though unit tests (which mock Prisma) don't catch it. The private addActionOwnershipToInputs (nested createMany) now only adds messagingChannelEmailAccountId. The public addActionOwnershipToInput (standalone action.create) still adds both fields. Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
emailAccountIdvia the compound FK[ruleId, emailAccountId]in nestedcreateManyunder Rule, so passing it explicitly is rejectedaddActionOwnershipToInputs(nested createMany) now only addsmessagingChannelEmailAccountId; the publicaddActionOwnershipToInput(standaloneaction.create) still adds both fieldsTest plan
🤖 Generated with Claude Code