You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the decoder will decode types to their AMQP type without regard to the field type data. Use the field type data to force the use of a restricted type when it is encountered. This will also eliminate the requires/provides validation errors currently being displayed.
The text was updated successfully, but these errors were encountered:
This issue currently shows up as a spurious validation error in two common cases:
WARNING: validation: Field "address" requires "address", but is not provided by value type "string"
and
WARNING: validation: Field "distribution-mode" requires "distribution-mode", but is not provided by value type "symbol"
These occur because these types are decoded on the wire as type string and type symbol respectively, but the AMQP specification requires that they be treated as restricted types address and distribution-mode respectively.
Currently the decoder will decode types to their AMQP type without regard to the field type data. Use the field type data to force the use of a restricted type when it is encountered. This will also eliminate the requires/provides validation errors currently being displayed.
The text was updated successfully, but these errors were encountered: