You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, great library! This is such a common use case that I can't believe there aren't go-to solutions out there. Hopefully this library becomes one.
I noticed that when using a connection string, e.g. /test?retryWrites=true, it should reference an existing database named test in mongo, but instead results in a new database being created with the name /test?retryWrites=true. Seems like the params from the ? on are being interpreted literally. Don't know if it's an issue with this library or a dependency.
The text was updated successfully, but these errors were encountered:
Hello @murtyjones,
Thank you for kind words!
Yes, I confirm, this is a bug in mongo-seeding. I will try to fix it in a few hours and release a new version 🙂
I've fixed the error and updated dependencies, but unfortunately I cannot do the release right now because of the following issue: DefinitelyTyped/DefinitelyTyped#26594
Can we wait a bit for a new release of mongo types? I think it will take one day at most. If this is urgent for you, then I can downgrade them and release new version.
First of all, great library! This is such a common use case that I can't believe there aren't go-to solutions out there. Hopefully this library becomes one.
I noticed that when using a connection string, e.g.
/test?retryWrites=true
, it should reference an existing database namedtest
in mongo, but instead results in a new database being created with the name/test?retryWrites=true
. Seems like the params from the?
on are being interpreted literally. Don't know if it's an issue with this library or a dependency.The text was updated successfully, but these errors were encountered: