Skip to content

fix(subject-mapping): fix hint and code nesting #903

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

Open
thejoeejoee wants to merge 1 commit into
base: master
Choose a base branch
from
Open

fix(subject-mapping): fix hint and code nesting #903

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 0 additions & 4 deletions nats-concepts/subject_mapping.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -100,7 +100,6 @@ When using **operator JWT security** (distributed security) with the built-in re
You can easily test individual subject transform rules using the [`nats`](../using-nats/nats-tools/nats\_cli/) CLI tool command `nats server mapping`. See examples below.
{% endhint %}

{% hint style="info" %}
From NATS server 2.11 (and NATS versions published thereafter) the handling of subjects, including mappings can be observed with `nats trace`

In the example below a message is first disambiguated from `orders.device1.order1` -> `orders.hub.device1.order1`. Then imported into a stream and stored under its original name.
Expand All @@ -121,9 +120,6 @@ Egress Count:

JetStream: 1
````
{% endhint %}



## Simple mappings

Expand Down