-
Notifications
You must be signed in to change notification settings - Fork 235
feat: bump driver to 4.x beta COMPASS-4805 #2269
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
Conversation
What does it mean? :) |
"debug": "^4.1.1", | ||
"lodash": "^4.17.15", | ||
"mongodb": "^3.6.3", | ||
"mongodb3": "npm:mongodb@^3.6.3", |
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 we 'copy-paste' the parse-connection-string.js
file and drop this one? We need to rework that to switch it to the new module anyway.
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.
I think we could... but I don't think we'd exactly want that to be the long-term solution here either, it's probably best to do some actual URL parsing based on mongodb-connection-string-url and then actually handle all the transformations here in the connection model directly (assuming that we keep mongodb-connection-model)
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.
but I don't think we'd exactly want that to be the long-term solution here either
Yeah i was thinking the same, we should definitely use the mongodb-connection-string-url
module instead.
(err, _client, tunnel, connectionOptions) => { | ||
if (err) { | ||
this._isConnected = false; | ||
this._isConnecting = false; |
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.
Nice :)
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.
Great! Should we merge now and get this in the next release? Or we prefer to wait?
As you prefer :) In any case, we should do at least one beta with this I would say. And I don't know if we want to actually do a compass GA release with a beta of the driver instead of a rc.0? |
There should be no issue with that. What does @mmarcon says? |
We are going to GA the shell with a beta of the driver, I think it's fine to ship Compass too. But yeah, let's definitely do a beta of compass with that before we do a GA. |
This is fairly functional already, but
e.g. the aggregation pipeline builder doesn't appear to work yet, andI have only checked a small subset of Compass's functionality here.Description
Checklist
Motivation and Context
Open Questions
Dependents
Types of changes