-
Notifications
You must be signed in to change notification settings - Fork 2
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
fix: update database schema file path in drizzle config files #31
Conversation
🦋 Changeset detectedLatest commit: ee81cf1 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
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.
Could you add a patch
changeset? npx changeset
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.
Looks like you commited a package-lock.json
-could you delete this?
I've made a note and will add package-lock.json
and yarn.lock
to the gitignore as we use a pnpm-lock.yaml
.
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.
Forgive my ignorance, first time contributing to a project, not familiar with this process, and thanks for the project.
No worries at all, thanks for the contribution - means a lot :) |
This should be live on npm now as of version
|
Update the database schema file path in drizzle config files to match the new path by including the
db
folder in the path and this will solve the issue #30 (not finding the schema file) that will happen on migration.