fix: Resolve issues with updates in mongo and @updatedAt fields #34
Conversation
This file contains 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
* created yarn scripts * prepared files structure to support 2 DBs
* fix test step in github workflow * add step to run mongo tests
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.
This pull request includes fixes for issues with updates when using MongoDB and the not working @updatedAt fields. Here's a summary of the changes:
fix: Resolve the issue with updates in MongoDB
Previously, updates were failing with an error about an unknown id arg (#28). This fix addresses the issue and ensures that updates work as expected.
fix: Automatically update @updatedAt fields with the current date
Previously, when a record was updated, the @updatedAt field was not automatically updated (SoftwareBrothers/adminjs#1452). This change resolves this issue.
feat(ci): Add Ci setup to run tests against MongoDB
Now CI runs tests against MongoDB (I used Mongo image from official Prisma examples) and Postgres. Here is an example of how this works.
fixes: #28
fixes: SoftwareBrothers/adminjs#1452
I want to ensure that these changes meet your expectations. If you prefer, I can remove the modifications made to the Prisma setup and GitHub workflow. Please let me know your thoughts.