Clarify support for Boolean JSON Schemas

[char0n]

Hello everybody,

OAS 3.1.1 just landed a clarification for Boolean JSON Schemas. IMHO AsyncApi 2.0.0 can also benefit by clarifying that Schema Object could be represented by additional values of true or false (Boolean JSON Schemas as later version of spec call it) . It's an important implication for tooling and JSON Schema Draft 7 explicitly allow to use Boolean JSON Schema. I guess using Boolean JSON Schemas in embedded Schema Objects is implicitly allowed, be we should explicitly clarify if Boolean JSON Schemas are also allowed as top levels schemas (e.g. #/components/schemas).

I'm currently working on tooling and the tooling I'm buiding already supports this as I assumed that Schema Object represents any JSON Schema as mandated by Draft 7, which includes Boolean JSON Schemas. We should either explicitly disallow or allow use of Boolean JSON Shemas within AsyncApi 2.0.0 spec to no leave space for different interpretations of tooling authors.

[magicmatatjahu]

@char0n Hello! As you wrote, AsyncAPI JSON Schema (aka Schema Object) is a superset of JSON Schema draft-07, so we should support Boolean schemas in the spec. I created a some time ago PR for clarify your (and mine) problem #550 We must wait for review from @derberg and @fmvilas. Also, please have in mind, that we have bug in parser-js, to which I also have PR with fix asyncapi/parser-js#311 and updated JSON Schema for spec asyncapi/spec-json-schemas#63

be we should explicitly clarify if Boolean JSON Schemas are also allowed as top levels schemas

In my PR I give you the possibility to use boolean wherever you can use Schema Object, also in channel/parameters/*/schema and message/payload and message/headers (this last must be of type object, but if you will use true it will mean that it can be object with ANY properties).

If you have any suggestion to PR, feel free to comment 😄

[char0n]

@magicmatatjahu thanks, so this looks like a duplicate then. Let's handle this in you PR. CLosing.