Publisher API about mojo-rabbitmq-client HOT 6 CLOSED

I'll opt for following signature:

publish($body!, \%headers?, *@params)

which will allow to call it like this:

->publish($body, { header => 'value' }, routing_key => 'something', 
                                        mandatory => 1, immediate => 0);
->publish($body, routing_key => 'something');
->publish($body, { header => 'value' });
->publish($body);

With following rules:

• if $body is hashref default content_type is set to application/json and $body is encoded to JSON string, otherwise it will be passed as-is,
• if second argument is hashref it will be merged with default headers, replacing any pre-existing values, if it's defined but not a hashref it will be treated as below,
• any other (slurpy) arguments will be treated as key/value pairs and merged with AMQP publish method default parameters

What do you think?

from mojo-rabbitmq-client.

I'm fine with that!
Do you want a PR with that or would you prefer to do it yourself?

from mojo-rabbitmq-client.

If you can, please write a PR - I don't have much spare time lately

from mojo-rabbitmq-client.

@tyldum Just make it flexible.

from mojo-rabbitmq-client.

In a5e148f I've changed publisher code to use ?routing_key= query parameter instead of ?queue=

from mojo-rabbitmq-client.

Resolved in 5a7cf91

from mojo-rabbitmq-client.