Skip to content

Releases: vitaly-t/connection-string

2.0.0

17 Mar 03:42
ec64bb4
Compare
Choose a tag to compare

Breaking Changes:

  • Implemented #9, i.e. isIPv6 flag was replaced with type = 'domain' | 'socket' | 'IPv4' | 'IPv6'
  • IPv6 addresses are no longer stripped of [], to keep them consistent with Literal IPv6 Spec
  • The library now also exports type HostType, to keep it friendly with TypeScript.

1.1.0

15 Mar 17:00
c1255f4
Compare
Choose a tag to compare
  • Implemented #10, by adding new option plusForSpace. See method toString for details.
  • Updated dependencies

v.1.0.1

19 Jul 13:46
Compare
Choose a tag to compare

Documentation updates only.

v.1.0.0

19 Jul 12:14
Compare
Choose a tag to compare
  • Renamed segments into path, for better compliance with the URL naming convention.
  • Explicitly disallow # to be in the URL, as URL fragments are not part of the URL connection string.

v.0.9.1

18 Jul 18:46
Compare
Choose a tag to compare

Documentation updates only.

v.0.9.0

17 Jul 15:58
Compare
Choose a tag to compare

Stop encoding $ by default

This release significantly improves on such delicate matter as $ symbols within the connection string.

Previous versions simply encoded $ as %24 by default, which is no longer the case. Symbol $ is no longer encoded by default, only when explicitly requested.

Method toString now accepts encoding options parameter, in which we can pass in {encodeDollar: true}, if we want all $ occurrences to be URL-encoded.

In addition, a host name now supports $ also.


It happens quite often that somebody uses $ in the user's password or in a URL parameter name, which gets encoded, and suddenly no longer works within the system. Although it is generally advised not to use $ for such purposes, it is best that at least by default that we do not encode it.

v.0.8.5

17 Jul 10:54
Compare
Choose a tag to compare

Documentation updates only.

v.0.8.4

16 Jul 22:41
Compare
Choose a tag to compare

Improving the logic of skipping invalid default hosts.

v.0.8.3

16 Jul 17:52
Compare
Choose a tag to compare

Specifically for parameter values, every + is now replaced with a space, to adhere to the URL spec.

So + and %20 within property values are now treated the same:

?message=Hello%20World!

?message=Hello+World!
//=> {params: {message: 'Hello World!'}}

v.0.8.2

16 Jul 14:57
Compare
Choose a tag to compare

Added static method parseHost, so hosts can be parsed independently.