6.0.0 (2019-06-18)
Bug Fixes
- adjusts namespaces and call signatures of "isValid" utils (c830ff6)
- improves explanatory comments (7870a99)
- uses native "url" module for URI parsing (5bd3333)
- uses new call signature of "validate()" in cli (4748564)
- validates relative URI (7344f12)
Features
- Adds validation of the "method" field (e5c4f72)
- Adds validation of the "uri" field (f08d0a6)
- Adds validation of the URI query parameters (1dfeab4)
- removes "callback" argument of "validate" (681b032)
- Uses "valid" instead of "isValid" on the top-level of a validation result to indicate the validity of the given message (969ab5a)
- removes "isValidatable" from public API (33dc9b8)
- removes "severity" from error messages (290dec8)
- removes "type" parameter from "validate" call signature (4a4e9a3)
- removes HttpRequest, HttpResponse, and Validatable (2c36cbb)
- stops using "isValid" internally (807a879)
- swaps the order of "real" and "expected" arguments (validate) (f631116)
BREAKING CHANGES
- Gavel no longer validates expected
statusMessage field
gavel.validate() no longer accepts a callback as an argument. Please use the "validate()" function as follows:
const result = gavel.validate(expected, real)
- Gavel's call signature of the "validate" now lists "expected" HTTP message and the first argument, and real HTTP message as the second argument:
- gavel.validate(real, expected)
+ gavel.validate(expected, real)
- Gavel no longer exports "HttpRequest" and "HttpResponse" classes. Use
gavel.validate instead.
- Calling
gavel.validate no longer requires the "type" parameter.
- Gavel no longer exports "isValid" method from public API. Please use
gavel.validate instead.
- Gavel no longer exposes "isValidatable" method in its public API
- Gavel validation result no longer contains the
version property
