Using dot notation keys without namespaces

[dbrxnds]

Hi,

We ran into an issue where we use dot notation for translations but with a flat messages json.

Wondering if there is a way to make next-intl aware that we use a flat object, so dot notation is ignored and just assumes regular key lookup.

[amannn]

Hi David,

nice to hear from you! Currently next-intl does not provide an option to configure a custom namespace character (see #105).

Any chance you could transform your flat messages file to a nested one? Here's a simplified transformation script for inspiration.

If we'd support dot notations in namespaces, a case like this would be ambiguous:

{
  "one.two": "12",
  "one": {"two": "12"}
}

That's why I'd like to avoid supporting it.

[amannn]

I see! Maybe you can use a default key for the ones that would overwrite a whole object (e.g. ADMIN.TITLE)?

[dbrxnds]

Figured that would be the best solution. That's what we ended up doing. Thanks!

[deammer]

@amannn sorry to necro this thread but the Code Sandbox you linked isn't available anymore. Would it be possible to share the code in here?

[amannn]

Oh yep, just updated the link above—thanks for the hint!

[deammer]

Super appreciated, thank you!