This object contains information about the operation representation in SNS.
Get JSON SchemaBundle| Identifier | https://schemas.sourcemeta.com/asyncapi/bindings/sns/0.1.0/operation.json |
|---|---|
| Base Dialect | Draft7 |
| Dialect | http://json-schema.org/draft-07/schema# |
| Health | |
| Size | 0.008475 MB |
This schema has 1 direct dependency and 0 indirect dependencies.
| Origin | Dependency |
|---|---|
/definitions/consumer/patternProperties/^x-[\w\d\.\x2d_]+$/$ref | /asyncapi/definitions/3.0.0/specificationextension |
This schema has 9 quality errors.
/examples/0blaze/valid_examplesOnly include instances in the `examples` array that validate against the schema
Invalid example instance at index 0 The array value was expected to validate against one and only one of the 3 given subschemas at instance location "/consumers/0/filterPolicy/event" at evaluate path "/properties/consumers/items/$ref/properties/filterPolicy/additionalProperties/oneOf" The object properties not covered by other adjacent object keywords were expected to validate against this subschema at instance location "/consumers/0/filterPolicy" at evaluate path "/properties/consumers/items/$ref/properties/filterPolicy/additionalProperties" Every item in the array value was expected to validate against the given subschema at instance location "/consumers" at evaluate path "/properties/consumers/items" The object value was expected to validate against the 4 defined properties subschemas at instance location "" at evaluate path "/properties"/definitions/consumer/properties/deliveryPolicy/descriptiondraft_ref_siblingsIn Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated
/definitions/consumer/properties/endpoint/descriptiondraft_ref_siblingsIn Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated
/definitions/consumer/properties/filterPolicyScope/enumenum_with_typeSetting `type` alongside `enum` is considered an anti-pattern, as the enumeration choices already imply their respective types
/definitions/consumer/properties/protocol/enumenum_with_typeSetting `type` alongside `enum` is considered an anti-pattern, as the enumeration choices already imply their respective types
/definitions/deliveryPolicy/properties/backoffFunction/enumenum_with_typeSetting `type` alongside `enum` is considered an anti-pattern, as the enumeration choices already imply their respective types
/definitions/redrivePolicy/properties/deadLetterQueue/descriptiondraft_ref_siblingsIn Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated
/properties/deliveryPolicy/descriptiondraft_ref_siblingsIn Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated
/properties/topic/descriptiondraft_ref_siblingsIn Draft 7 and older dialects, keywords sibling to `$ref` are never evaluated