Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Options property inboxPrefix not implemented in ClientNats #13150

Closed
3 of 15 tasks
leandrogenas opened this issue Feb 1, 2024 · 1 comment
Closed
3 of 15 tasks

Options property inboxPrefix not implemented in ClientNats #13150

leandrogenas opened this issue Feb 1, 2024 · 1 comment
Labels
needs triage This issue has not been looked into

Comments

@leandrogenas
Copy link
Contributor

leandrogenas commented Feb 1, 2024 •
edited

Is there an existing issue for this?

  • I have searched the existing issues

Current behavior

The message is not being published with the set inbox prefix

Minimum reproduction code

https://github.com/n-a

Steps to reproduce

  1. Publish any message to a Nats server with inboxPrefix option defined

No response

Expected behavior

The message being written with the correct prefix

Package

  • I don't know. Or some 3rd-party package
  • @nestjs/common
  • @nestjs/core
  • @nestjs/microservices
  • @nestjs/platform-express
  • @nestjs/platform-fastify
  • @nestjs/platform-socket.io
  • @nestjs/platform-ws
  • @nestjs/testing
  • @nestjs/websockets
  • Other (see below)

Other package

No response

NestJS version

No response

Packages versions

[System Information]
OS Version : Windows 10
NodeJS Version : v20.9.0
YARN Version : 1.22.19

[Nest CLI]
Nest CLI Version : 8.2.8

[Nest Platform Information]
platform-express version : 9.4.3
platform-fastify version : 9.4.3
microservices version : 9.4.3
serve-static version : 3.0.1
schematics version : 9.2.0
passport version : 9.0.3
typeorm version : 9.0.1
testing version : 9.4.3
common version : 9.4.3
core version : 9.4.3
jwt version : 10.2.0
cli version : 8.2.8

Node.js version

No response

In which operating systems have you tested?

  • macOS
  • Windows
  • Linux

Other

No response
@leandrogenas leandrogenas added the needs triage This issue has not been looked into label Feb 1, 2024
@leandrogenas leandrogenas mentioned this issue Feb 1, 2024
Merged
12 tasks
@kamilmysliwiec
Copy link
Member

Let's track this here #13151

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
needs triage This issue has not been looked into
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kamilmysliwiec @leandrogenas