From cd2962639c2c73a67010cab711a6381775cfcb3e Mon Sep 17 00:00:00 2001 From: Pavel Bodiachevskii Date: Mon, 19 Feb 2024 15:57:53 +0400 Subject: [PATCH] docs: fix Specification Extensions Field Pattern (#1035) Co-authored-by: Sergio Moya <1083296+smoya@users.noreply.github.com> --- spec/asyncapi.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spec/asyncapi.md b/spec/asyncapi.md index bd7bada5..3b6bd38f 100644 --- a/spec/asyncapi.md +++ b/spec/asyncapi.md @@ -2647,7 +2647,7 @@ The extensions properties are implemented as patterned fields that are always pr Field Pattern | Type | Description ---|:---:|--- -`^x-[\w\d\-\_]+$` | Any | Allows extensions to the AsyncAPI Schema. The field name MUST begin with `x-`, for example, `x-internal-id`. The value can be `null`, a primitive, an array or an object. Can have any valid JSON format value. +`^x-[\w\d\.\x2d_]+$` | Any | Allows extensions to the AsyncAPI Schema. The field name MUST begin with `x-`, for example, `x-internal-id`. The value can be `null`, a primitive, an array or an object. Can have any valid JSON format value. The extensions may or may not be supported by the available tooling, but those may be extended as well to add requested support (if tools are internal or open-sourced).