Feature/ssl param

[justinmchase]

When you create an Azure cosmos db it gives you a connection string like this:

mongodb://example:<redacted>@example.mongo.cosmos.azure.com:10255/?ssl=true&replicaSet=globaldb&retrywrites=false&maxIdleTimeMS=120000&appName=@example@

However when you try to use this connection string to actually connect it basically hangs indefinitely. After some debugging I figured out that the connection string parsing is simply not handling the ssl=true parameter. Simply setting tls = true in this case allows deno_mongo to successfully connect to azure cosmosdb.

[justinmchase]

A couple other things I noticed by didn't touch:

• azure's connection string has retrywrites instead of retryWrites and this libraries parse function is case sensitive.
• This library emits no errors or warnings for parameters in the connection string it doesn't support or understand.
• The connection hangs with no timeouts and no errors in the case of a bad connection string
• You've wrapped all your unit tests in a function then import that function and invoke it... In the latest version of Deno this makes it harder to just run the tests for a single file

[erfanium]

@justinmchase Thank you Justin for making this PR
Is this PR mergeable or you are still working on it? because there is some failed tests here

this libraries parse function is case sensitive

This library emits no errors or warnings for parameters in the connection string it doesn't support or understand.

The connection hangs with no timeouts and no errors in the case of a bad connection string

It's welcome to fix all of these issues, if your expected behaviors are a part of MongoDB standard driver specifications

You've wrapped all your unit tests in a function then import that function and invoke it... In the latest version of Deno this makes it harder to just run the tests for a single file

yes, really not a good design, PR is welcome :-)

[justinmchase]

My bad, I thought I re-ran the test but apparently I didn't. I fixed it now but some other test is not succeeding. Locally its passing and in 3/4 versions of ubuntu it seems to be passing. I'm not sure what to do about it. It seems unrelated to this change.

[erfanium]

Thank you Justin. That's awesome

[erfanium]

@lucsoft
Is it good to you?

[lucsoft]

I mean it's fixes the issue but we need to refactor the parser lmao

But this is not a scope for this PR

[justinmchase]

Thanks everyone.