v5.0.1

What's Changed

• fix issue when multiple operations use same channel by @WaleedAshraf in #67

Full Changelog: v5.0.0...v5.0.1

v5.0.0

Breaking:

• Errors message format for the initial check on the AsyncApi document has been updated.
  • Note: No change in errors thrown from the validate() method.
• Deprecate the validateByMessageId() method as messageId was removed in AsyncApi v3.0.0. More details here asyncapi/spec/issues/978

New / Improvements:

• Support AsyncAPI schema v3.0.0
• Start using @asyncapi/parser v3

v4.0.0

Breaking:

• "should" replaced with "must" in the error messages, as per in AJV

New / Improvements:

• Support AsyncAPI schema v2.4.0
• Added validateByMessageId() method, which only requires key and value. To use this method, your AsyncAPI schema should be >= 2.4.0. messageId should be defined in schema as per AsyncAPI 2.4.0 schema definition.
• msgIdentifier option is only required if you use .validate() method.
• You can use both validateByMessageId() and validate() methods if your AsyncAPI schema version is >= 2.4.0
• Start using ajv-formats for custom formats.

v3.2.0

• Add an option to provide path parameter for relative ref.

v3.1.1

• Add TS types
• Fix JSDocs for fromSource()

v3.1.0

• Add support for deserialized objects as a source
• Update libs to the latest version

v3.0.0

Version 3.0.0 (2021-03-20)

Breaking:

• Remove support for AsyncAPI Schema v1.2.0
• Remove ._schema property from instance. Use .schema instead.

New / Improvements:

• channel, operation and options.msgIdentifier are required for validation.
• Add support for OpenAPI formats
• Using @asyncapi/openapi-schema-parser and @asyncapi/parser

v2.5.0

• Provide .schema property on the instance, to access ref resolved JSON schema.
• Add deprecation message for AsyncAPI v1.

v2.4.5

• remove Travis integration
• use Github actions for testing and coverage report
• add CodeQL check

v2.4.4

• Deprecate version < 2.4.2
• Add missing tests
• Update docs