v3.0.0

3.0.0 (2019-06-17)

Bug Fixes

• adds proper indentation for "response.feature" (8796e68)
• includes "isValid" key in expected validation result (validators) (6a8ed7c)
• includes relative URI in feature definition (f7ffc14)
• removes duplicate "will (NOT) set errors on "X") criteria (bb81f9d)
• renames "body" to "headers" in validity assertion (headers) (dcda152)
• stores HTTP message fields under "fields" property, not "field" (7823856)
• uses implementation-agnostic phrasing for field validity definition (808ad9e)
• uses non-implementational behavior descriptions for body expectations (2a8475d)
• wraps target property in quotes (da01736)

Features

• adds "method" expectation suite (9c1f450)
• adds "uri" validation feature (cf50d5e)
• adds "uri" validation feature suite (f584714)
• lists HTTP message fields under "field" key (bcd5c9e)
• remove "isValid" from public API (ac26d1d)
• removes "isValidatable" from public API (e84a0cf)
• removes "severity" property from validation errors (2a364e2)
• removes "version" from validation results (d581f81)
• removes async API (8feb224)
• removes references to "HttpRequest" and "HttpResponse" classes (f77a112)
• removing "data_model" feature (8711aa1)
• replaces "results" key with "errors" (9c91c7d)
• sets "isValid" property on each HTTP message field result (c5663f6)
• swaps the order of "real" and "expected" arguments of "validate" (1f2d29f)

BREAKING CHANGES

• Gavel spec no longer has "data_model" feature describing operable HTTP messages.
• Gavel's "validate" method now has the following call signature:
  validate(expected, real)
• Validation errors no longer have "severity" property.
• Validation errors of each individual HTTP message field are now listed in the "errors" key
• Validation result now lists validated HTTP message fields under "field" key
• Removes "isValidatable" from public API