Using constants in translations

Just started integrating this into our project, and it's fitting much of our use criteria except one key issue around our company / brand name.

We've just had to reword the name of our company from "Company Name" to "Other Detail: Company Name" in our app because of reasons out of our control. This means we've had to change every area that had "Company Name" in.

What would be amazing would be some way to "refer back" to another translation's entry.

As in, in your app's dictionary ,

import { type DeclarationContent } from "intlayer"

const appContent = {
  key: "app",

  content: {
    brandName: "Other Detail: Company Name",
    brandNameShort: "Company Name",
  }
} satisfies DeclarationContent

export default appContent

And then, in another page/component, you can pull that in,

import { DeclarationContent } from "intlayer"

const overviewContent = {
  key: "overview",
  content: {
    header: "Do all this awesome stuff with %%{app.brandName}%%",
    subHeader: "With %%{app.brandNameShort}%%, you'll be even more awesomer!"
  }
} satisfies DeclarationContent

export default overviewContent

Make sense?

Also, just checking on the status of the online editor? I tried setting up there but ran into a number of hangs and errors, and can't create an organisation, or new project at all.

No files, tests, or entry points are named. Start by reviewing the translation/content reference examples in the issue and the existing handling of translation values; clarify the reference syntax and scope before implementation. Done means one translation can reuse another value reliably, with coverage for the shown brand-name cases and the online-editor concerns separated.