fix demo seed conflicting with dev seed #9087
Merged
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.
We have conflicts which prevents us from running demo seed command after a database-reset or/and if dev seed has already been populated. This is because we are trying to create Tim user twice (but due to the insert()...onConflict() in the seed creation, it does not create the second one), for seed-dev and seed-demo .
This PR fixes that by using the same user id, allowing us to use the same Tim apple for both dev/demo seeds
Test