routing key mismatch when using custom setup function

[skif48]

origin issue #3
@marcio199226 comment:

I have used a custom setup function

  consumerFactory.setCustomSetupFunction(async (connection) => {
    const channel = await connection.createChannel();
    await channel.assertExchange('exchange', 'topic', { durable: true });
    const queueMetadata = await channel.assertQueue('input', {
      durable: true,
      maxPriority: 10
    });

    await channel.bindQueue(queueMetadata.queue, 'exchange', 'account.*');
    await channel.prefetch(1);

    return {channel, prefetch: 1, autoAck: false, queue: 'input'};
  });

And after consuming some message, message.fields.routingKey returns my queue name "input" insteaf of currently messgae routingKey

I have used 0.1.2v

Best regards

[skif48]

@marcio199226, could you please provide a snippet on how you publish messages too?

[marcio199226]

    await publisher.publishMessage(
      Buffer.from(JSON.stringify(payload)),
      routingKey,
      {
        persistent: true,
        headers: {
          'x-created-at': moment(new Date()).format('DD/MM/YYYY HH:mm:ss')
        }
      }
    );

Where routingKey may be optional

[skif48]

Hey, @marcio199226. By optional routingKey you mean empty string?

[skif48]

I just tested your custom setup functions locally and it worked just fine. I managed to receive all the messages I've published, and the routing key contained account. part. How do you set up your publisher instance?

[marcio199226]

Hey, @marcio199226. By optional routingKey you mean empty string?

I mean it could be null or a string

I just tested your custom setup functions locally and it worked just fine. I managed to receive all the messages I've published, and the routing key contained account. part. How do you set up your publisher instance?

My publisher is an php application, so when i'm consuming messages i have this issue (i'm sure that messages which nodejs consumes has routing key)