-
Notifications
You must be signed in to change notification settings - Fork 18
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
nice error on nested triggers #348
Open
ldanilek
wants to merge
1
commit into
main
Choose a base branch
from
lee/error-on-nested-triggers
base: main
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.
+38
−0
Open
Changes from all commits
Commits
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
There are no files selected for viewing
This file contains 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 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -90,6 +90,15 @@ export class Triggers< | |
} | ||
|
||
wrapDB = <C extends Ctx>(ctx: C): C => { | ||
if (wrapDBCalled) { | ||
throw new Error( | ||
`Triggers.wrapDB called multiple times in a single mutation. Not allowed due to potential deadlock. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think this could merit a specific example of what this looks like, maybe just in the triggers docs? And we could link to it from the error message? Like Troubleshooting:
|
||
Call it once in a single \`customMutation\`. | ||
Do not call mutations directly as functions. | ||
See https://docs.convex.dev/production/best-practices/#use-helper-functions-to-write-shared-code`, | ||
); | ||
} | ||
wrapDBCalled = true; | ||
return { ...ctx, db: new DatabaseWriterWithTriggers(ctx, ctx.db, this) }; | ||
}; | ||
} | ||
|
@@ -148,6 +157,7 @@ class Lock { | |
let innerWriteLock = new Lock(); | ||
let outerWriteLock = new Lock(); | ||
const triggerQueue: (() => Promise<void>)[] = []; | ||
let wrapDBCalled = false; | ||
|
||
export class DatabaseWriterWithTriggers< | ||
DataModel extends GenericDataModel, | ||
|
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.
nit: I'd be less aggressive on the regex because I find it annoying to have to update the test whenever the error message changes. Maybe just checking the first sentence + checking a link to docs shows up in there somewhere?