Seed database after configuring triggers - #189
Merged
mbrandonw merged 2 commits intoSep 16, 2025
Merged
Conversation
mbrandonw
approved these changes
Sep 16, 2025
mbrandonw
reviewed
Sep 16, 2025
| }) | ||
| .execute(db) | ||
|
|
||
| if context == .preview { |
Member
There was a problem hiding this comment.
I switched this to only seeding in previews cause it turns out we seed in tests already. and probably best to leave tests responsible for seeding, especially if they want to seed differently from previews.
Contributor
Author
There was a problem hiding this comment.
Ha, it's actually why I asked but I should've mentioned my reasoning in Slack. Great!
mbrandonw
approved these changes
Sep 16, 2025
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
2 participants
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.
No description provided.