Releases: vitaly-t/connection-string
Releases · vitaly-t/connection-string
v.0.8.1
Improved URL Validation
Now any invalid character in the URL is detected, and reported along with the position.
Also updated:
v.0.8.0
Breaking Changes
- Replaced method
build()
with toString()
- Added method
toString()
to each individual host object.
v.0.7.0
Improved support for IPv6 addresses.
Now each host also comes with property isIPv6
, to allow for a more logical address processing.
When only the port is specified, but no host name, isIPv6
is not specified either.
v.0.6.1
- Minor code refactoring
- Making support for Node.js 4.0 (or later) more explicit, i.e. Node.js 10.x and 12.x are not supported.
- Documentation updates.
0.6.0
This is a breaking change.
The protocol has been updated to support multiple hosts, in the same way as here.
v.0.5.3
- Added stricter defaults parsing for
params
, port
and hostname
- Made
host
impossible to set via defaults directly. Only hostname
and port
can be set now, while host
is now set automatically.
- Changed TypeScript declarations. Type
IConnectionString
is now IConnectionDefaults
, as it is now only a sub-set of the protocol for setting defaults.
v.0.5.2
Fixing Number.isInteger
polyfill for older browsers.
v.0.5.1
Making rules within setDefaults
more strict.
For example, port
won't be updated, unless the default value is an integer between 0 and 65535.
Also, the defaults will no longer be used for properties that exist in general, even if they are set as empty.
v.0.5.0
This is a major update, which now makes it possible to exchange objects of any complexity through URL parameters automatically, plus use merging logic for parameters.
When setting defaults (method setDefaults
):
- Empty segments are now skipped
- Parameters that do not exist are now merged with the ones that exist
When building a string (method build
):
- Parameter values (
params
) that are not strings, are first converted into a JSON string, and then URL-encoded.
v.0.4.2
- Fixed #2
- Improved tests
- Updated dependencies