Allow named components in Trans in @lingui/macro

[fdev]

The documentation of Trans has the following example:

<Trans id="Read the <0>docs</0>." components={{0: <a href="/docs" />}} />

Since the number tags don't provide much context to the translator I was hoping I could use named tags instead as such:

<Trans id="Read the <link>docs</link>." components={{link: <a href="/docs" />}} />

Unfortunately, it seems only numbered tags are supported.

[semoal]

Yep, it's a nice addition. Also related to #1185

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[fdev]

I'm replying to keep this issue from going stale. I would still like to see this implemented.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[fdev]

I'm replying (again) to keep this issue from going stale. I would still like to see this implemented.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[fdev]

I'm replying (again again) to keep this issue from going stale. I would still very much like to see this implemented.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[thekip]

According to the docs this should be already supported look at last line in the list https://lingui.js.org/releases/migration-3.html#lingui-react

Did you try it with version 3?

[Martin005]

@thekip The Trans component in @lingui/macro doesn't currently support it.
On the other hand, the Trans component in @lingui/react should support it as mentioned in the Migration guide you posted, but it is not working there. I have created an issue #1400 which describes the issue in @lingui/react.

Let's leave this issue for implementing the "named components" in the Trans component in @lingui/macro.

[thekip]

@Martin005 it's unrelated to macro.

[andrii-bodnar]

it's unrelated to macro.

@thekip could you please explain in more detail what you mean?

[thekip]

it was never asked for the Macro. The topic starter mentioned the doc of the macro because there are examples how macro transpiled to component, but the actual question was about component, not a macro.

Macro doesn't pass thru itself components and values properties, they are populated automatically.

Implementing named components in macro it's a separate feature which should be carefully designed.