Add (initial) support for Dry run mode #867
Draft
+178
−0
Conversation
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
dereuromark
reviewed
Jul 18, 2025
dereuromark
reviewed
Jul 18, 2025
dereuromark
reviewed
Jul 18, 2025
jamisonbryant
force-pushed
the
dry-run-mode
branch
from
a12460f to
c5b6e19
Compare
jamisonbryant
force-pushed
the
dry-run-mode
branch
from
63e05e8 to
c315363
Compare
jamisonbryant
force-pushed
the
dry-run-mode
branch
from
c315363 to
83bb76c
Compare
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.
At $MYJOB, we approach seeds a little differently. We have created a custom
AppSeedthat all seeds inherit from that only runs INSERT and UPDATE queries as needed, rather than the more typical DELETE ALL/INSERT style.Like with migrations, we want the ability to be able to run seeds in dry-run mode, so we can see the queries that would run before executing them. This PR attempts to add this behavior to the plugin.
I added some new tests and they are MOSTLY passing (save for two, but seemingly for an unrelated reason). The ones that are outright failing are existing tests for reasons like "database is locked" which I'm unsure how to resolve. Any tips would be appreciated.