Where should properties like message_id, correlation_id, etc. be set in an amqp message? about rhea HOT 7 CLOSED

Yes that is correct, the properties are all top level objects. There is some tension between closely following the spec and making the library intuitive for users who don't know the spec. The properties were one such trade-off. (At one point rhea supported both, but that ended up being more confusing)

from rhea.

Oops. Can this be documented in the README.md? This would help other people. Typescript type definitions would have been so useful in this case.
Thank you so much for all the prompt responses.

from rhea.

/cc @anthonyvercolano - message_id will be a top level property.

from rhea.

The README.md does briefly describe the message fields in text for Sender.send(). Would probably be clearer to have a distinct section on message format and refer to that from relevant places.

from rhea.

@grs - Some follow up questions:

• How should predefined properties actually be serialized on the wire? Does message_id go under properties (rhea does it for us)? or it actually remains as a top level property on the wire as well?
• What about application_properties and message_annotations? Should they be flattened as well or should remain inside their property names?

I am still a newbie with AMQP hence some of those questions may seem silly..

from rhea.

rhea will encode everything correctly on the wire i.e. properties will be in a proper properties section.

application-properties and message-annotations are in nested maps as the names of those are not known in advance

from rhea.

cool that makes sense. Thank you :).

from rhea.