Skip to content
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

#4 Duplicate entries seeded #4

Open
Nick-StormID opened this issue Sep 28, 2022 · 0 comments · May be fixed by #5
Open

#4 Duplicate entries seeded #4

Nick-StormID opened this issue Sep 28, 2022 · 0 comments · May be fixed by #5

Comments

@Nick-StormID
Copy link

If the candidate runs npm i more than once, the three test TODOs are duplicated by the seeding step.
To avoid these duplications, and the confusion that can occur when these duplicates appear, I suggest we clear the db prior to seeding.

An implication of this is that any entries added by the candidate through their UI as they develop a solution will be cleared/lost.
For the intended use of this project I see this as a lesser issue than the duplicate entries. Nevertheless, this side effect should be indicted in the README.

@Nick-StormID Nick-StormID changed the title #1 Duplicate entries seeded #4 Duplicate entries seeded Sep 28, 2022
@Nick-StormID Nick-StormID linked a pull request Sep 29, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant