feature - Support for JSON parameter in MSSQL connection string

[ByteOPCode]

Issue:

The existing parser implementation does not parse the nested properties from the connection string for MSSQL (Tedious supports properties like InstanceName, TDS Packet size, readOnlyIntent under options key, which can not be passed to knex over connection string at the moment).

Example Connection string :

mssql://user:password@host/database?domain=testDomain&options={"instanceName": "TestInstance001", "readOnlyIntent": true}'

Actual Config

{
  user: 'user',
  password: 'password',
  database: 'database',
  server: 'host',
  domain: 'testDomain',
  options:'{"instanceName": "TestInstance001", "readOnlyIntent": true}'
}

Expected Config

{
  user: 'user',
  password: 'password',
  database: 'database',
  server: 'host',
  domain: 'testDomain',
  options: {
    instanceName: 'TestInstance001'
    trustServerCertificate: true
  }
}

[coveralls]

Coverage remained the same at 92.223% when pulling ada10b0 on ByteOPCode:master into 8bb9e83 on knex:master.

[OlivierCavadenti]

thx for the PR !

[ByteOPCode]

Hi, may I know - when can we have a release ?

[kibertoad]

Released in 2.2.0