The open alternative to Salesforce, designed for AI.
TypeScript crmcrm-systemcustomergood-first-issuegraphqlhacktoberfestjavascriptmarketingmonoreponestjsopen-sourcepostgresqlreactreactjssalestypescriptweb
i18n - docs translations (#20095)
github-actions[bot]350b835fbcdf
diff --git a/packages/twenty-docs/l/de/developers/extend/apps/logic-functions.mdx b/packages/twenty-docs/l/de/developers/extend/apps/logic-functions.mdxindex 7502c27b2e0..ea0f909f023 100644--- a/packages/twenty-docs/l/de/developers/extend/apps/logic-functions.mdx+++ b/packages/twenty-docs/l/de/developers/extend/apps/logic-functions.mdx@@ -94,16 +94,16 @@ const handler = async (event: RoutePayload) => {Der Typ `RoutePayload` hat die folgende Struktur:- | Eigenschaft | Typ | Beschreibung | Beispiel |- | ---------------------------- | ------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- |- | `headers` | `Record\<string, string \| undefined>` | HTTP-Header (nur die in `forwardedRequestHeaders` aufgelisteten) | siehe Abschnitt unten |- | `queryStringParameters` | `Record\<string, string \| undefined>` | Query-String-Parameter (mehrere Werte mit Kommas verbunden) | `/users?ids=1&ids=2&ids=3&name=Alice` -> `{ ids: '1,2,3', name: 'Alice' }` |- | `pathParameters` | `Record\<string, string \| undefined>` | Aus dem Routenmuster extrahierte Pfadparameter | `/users/:id`, `/users/123` -> `{ id: '123' }` |- | `body` | `object \| null` | Geparster Request-Body (JSON) | `{ id: 1 }` -> `{ id: 1 }` |- | `rawBody` | `string \| undefined` | Original UTF-8 request body, before JSON parsing. Useful for verifying HMAC-style webhook signatures (e.g. GitHub's `X-Hub-Signature-256`, Stripe). `undefined` when the runtime did not preserve it. | |- | `isBase64Encoded` | `boolean` | Gibt an, ob der Body Base64-codiert ist | |- | `requestContext.http.method` | `Zeichenkette` | HTTP-Methode (GET, POST, PUT, PATCH, DELETE) | |- | `requestContext.http.path` | `Zeichenkette` | Rohpfad der Anfrage | |+ | Eigenschaft | Typ | Beschreibung | Beispiel |+ | ---------------------------- | ------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- |+ | `headers` | `Record\<string, string \| undefined>` | HTTP-Header (nur die in `forwardedRequestHeaders` aufgelisteten) | siehe Abschnitt unten |+ | `queryStringParameters` | `Record\<string, string \| undefined>` | Query-String-Parameter (mehrere Werte mit Kommas verbunden) | `/users?ids=1&ids=2&ids=3&name=Alice` -> `{ ids: '1,2,3', name: 'Alice' }` |+ | `pathParameters` | `Record\<string, string \| undefined>` | Aus dem Routenmuster extrahierte Pfadparameter | `/users/:id`, `/users/123` -> `{ id: '123' }` |+ | `body` | `object \| null` | Geparster Request-Body (JSON) | `{ id: 1 }` -> `{ id: 1 }` |+ | `rawBody` | `string \| undefined` | Ursprünglicher UTF-8-Request-Body vor dem JSON-Parsing. Nützlich zur Verifizierung von Webhook-Signaturen im HMAC-Stil (z. B. GitHubs `X-Hub-Signature-256`, Stripe). `undefined`, wenn die Laufzeitumgebung es nicht beibehalten hat. | |+ | `isBase64Encoded` | `boolean` | Gibt an, ob der Body Base64-codiert ist | |+ | `requestContext.http.method` | `Zeichenkette` | HTTP-Methode (GET, POST, PUT, PATCH, DELETE) | |+ | `requestContext.http.path` | `Zeichenkette` | Rohpfad der Anfrage | |#### forwardedRequestHeadersdiff --git a/packages/twenty-docs/l/pt/user-guide/data-model/how-tos/create-many-to-many-relations.mdx b/packages/twenty-docs/l/pt/user-guide/data-model/how-tos/create-many-to-many-relations.mdxindex 7cd9e15efcd..f5269e5c559 100644--- a/packages/twenty-docs/l/pt/user-guide/data-model/how-tos/create-many-to-many-relations.mdx+++ b/packages/twenty-docs/l/pt/user-guide/data-model/how-tos/create-many-to-many-relations.mdx@@ -53,9 +53,9 @@ Primeiro, crie o objeto intermediário que manterá as conexões.1. Vá a **Definições → Modelo de Dados**2. Clique em **+ Novo objeto**3. Dê um nome descritivo (por exemplo, "Atribuição de Projeto", "Membro da Equipe", "Pedido de Produto")-4. Toggle "Skip creating a Name field" on+4. Ative a opção "Ignorar a criação de um campo Nome"-<img src="/images/user-guide/fields/new-pivot-object.png" alt="New pivot object" />+<img src="/images/user-guide/fields/new-pivot-object.png" alt="Novo objeto pivô" />5. Clique em **Salvar**@@ -63,27 +63,27 @@ Primeiro, crie o objeto intermediário que manterá as conexões.**Convenção de nomenclatura**: Use um nome que descreva a relação, como "Atribuição de Projeto" ou "Participação na Equipe". Isso torna o modelo de dados mais fácil de entender.</Tip>-## Step 2: Create Relations Between Objects and the Junction+## Etapa 2: Crie relações entre os objetos e o objeto de junção-Add relation fields from each of your two objects to the junction object.+Adicione campos de relação de cada um dos seus dois objetos ao objeto de junção.-### First Relation (Object A → Junction)+### Primeira Relação (Objeto A → Junção)-1. Select your first object in **Settings → Data Model**-2. Click **+ Add Relation**-3. Select the junction object (e.g., "Project Assignments")-4. Set the relation type to **One-To-Many** (one person can link to many assignments)+1. Selecione seu primeiro objeto em **Settings → Data Model**+2. Clique em **+ Adicionar relação**+3. Selecione o objeto de junção (por exemplo, "Atribuições de Projeto")+4. Defina o tipo de relação como **Um-para-muitos** (uma pessoa pode se vincular a muitas atribuições)5. Nomeie os campos:* Campo em Pessoas: por exemplo, "Atribuições de Projeto"* Campo na junção: por exemplo, "Pessoa"6. Clique em **Salvar**-### Second Relation (Object B → Junction)+### Segunda Relação (Objeto B → Junção)-1. Select your second object in **Settings → Data Model**-2. Click **+ Add Relation**-3. Select the junction object (e.g., "Project Assignments")-4. Set the relation type to **One-To-Many** (one project can link to many assignments)+1. Selecione seu segundo objeto em **Settings → Data Model**+2. Clique em **+ Adicionar relação**+3. Selecione o objeto de junção (por exemplo, "Atribuições de Projeto")+4. Defina o tipo de relação como **Um-para-muitos** (um projeto pode se vincular a muitas atribuições)5. Ative **"Esta é uma relação com um objeto de junção"**<img src="/images/user-guide/fields/junction-relation-toggle.png" style={{width:'100%'}} />@@ -125,13 +125,13 @@ Aqui está um passo a passo completo:### Adicionar Relações-1. **People → Project Assignment**- * Type: One-to-Many+1. **Pessoas → Atribuição de Projeto**+ * Tipo: Um-para-muitos* Campo em Pessoas: "Atribuições de Projeto"* Campo em Atribuição: "Pessoa"-2. **Projects → Project Assignment**- * Type: One-to-Many+2. **Projetos → Atribuição de Projeto**+ * Tipo: Um-para-muitos* Campo em Projetos: "Membros da Equipe"* Campo em Atribuição: "Projeto"diff --git a/packages/twenty-docs/l/ru/user-guide/data-model/how-tos/create-many-to-many-relations.mdx b/packages/twenty-docs/l/ru/user-guide/data-model/how-tos/create-many-to-many-relations.mdxindex b685587375c..b01d76e78ef 100644--- a/packages/twenty-docs/l/ru/user-guide/data-model/how-tos/create-many-to-many-relations.mdx+++ b/packages/twenty-docs/l/ru/user-guide/data-model/how-tos/create-many-to-many-relations.mdx@@ -53,9 +53,9 @@ People ←→ Project Assignments ←→ Projects1. Перейдите в **Настройки → Модель данных**2. Нажмите **+ Новый объект**3. Дайте ему понятное имя (например, "Project Assignment", "Team Member", "Product Order")-4. Toggle "Skip creating a Name field" on+4. Включите переключатель «Пропустить создание поля „Имя“»-<img src="/images/user-guide/fields/new-pivot-object.png" alt="New pivot object" />+<img src="/images/user-guide/fields/new-pivot-object.png" alt="Новый объект-связка" />5. Нажмите **Сохранить**@@ -63,27 +63,27 @@ People ←→ Project Assignments ←→ Projects**Рекомендации по именованию**: Используйте название, описывающее связь, например "Project Assignment" или "Team Membership". Так модель данных становится более понятной.</Tip>-## Step 2: Create Relations Between Objects and the Junction+## Шаг 2: Создайте связи между объектами и объектом-связкой-Add relation fields from each of your two objects to the junction object.+Добавьте поля связи из каждого из двух объектов в объект-связку.-### First Relation (Object A → Junction)+### Первая связь (Объект A → Объект-связка)-1. Select your first object in **Settings → Data Model**-2. Click **+ Add Relation**-3. Select the junction object (e.g., "Project Assignments")-4. Set the relation type to **One-To-Many** (one person can link to many assignments)+1. Выберите ваш первый объект в **Настройках → Модель данных**+2. Нажмите **+ Добавить связь**+3. Выберите объект-связку (например, "Назначения по проектам")+4. Установите тип связи **Один-ко-многим** (один человек может быть связан со многими назначениями)5. Назовите поля:* Поле в объекте Люди: например, "Project Assignments"* Поле на объекте-связке: например, "Person"6. Нажмите **Сохранить**-### Second Relation (Object B → Junction)+### Вторая связь (Объект B → Объект-связка)-1. Select your second object in **Settings → Data Model**-2. Click **+ Add Relation**-3. Select the junction object (e.g., "Project Assignments")-4. Set the relation type to **One-To-Many** (one project can link to many assignments)+1. Выберите ваш второй объект в **Настройках → Модель данных**+2. Нажмите **+ Добавить связь**+3. Выберите объект-связку (например, "Назначения по проектам")+4. Установите тип связи **Один-ко-многим** (один проект может быть связан со многими назначениями)5. Включите **"Это связь с объектом-связкой"**<img src="/images/user-guide/fields/junction-relation-toggle.png" style={{width:'100%'}} />@@ -125,13 +125,13 @@ Add relation fields from each of your two objects to the junction object.### Добавьте связи-1. **People → Project Assignment**- * Type: One-to-Many+1. **Люди → Назначение на проект**+ * Тип: Один-ко-многим* Поле в объекте Люди: "Project Assignments"* Поле в объекте Assignment: "Person"-2. **Projects → Project Assignment**- * Type: One-to-Many+2. **Проекты → Назначение на проект**+ * Тип: Один-ко-многим* Поле в объекте Проекты: "Team Members"* Поле в объекте Assignment: "Project"diff --git a/packages/twenty-docs/l/tr/user-guide/data-model/how-tos/create-many-to-many-relations.mdx b/packages/twenty-docs/l/tr/user-guide/data-model/how-tos/create-many-to-many-relations.mdxindex ebe90e4a392..723d72928a1 100644--- a/packages/twenty-docs/l/tr/user-guide/data-model/how-tos/create-many-to-many-relations.mdx+++ b/packages/twenty-docs/l/tr/user-guide/data-model/how-tos/create-many-to-many-relations.mdx@@ -53,9 +53,9 @@ Bağlantı ilişkisi anahtarını etkinleştirdiğinizde, Twenty aradaki bağlan1. **Ayarlar → Veri Modeli** bölümüne gidin2. **+ Yeni nesne**'ye tıklayın3. Açıklayıcı bir ad verin (örn. "Project Assignment", "Team Member", "Product Order")-4. Toggle "Skip creating a Name field" on+4. "Ad alanı oluşturmayı atla" seçeneğini açın-<img src="/images/user-guide/fields/new-pivot-object.png" alt="New pivot object" />+<img src="/images/user-guide/fields/new-pivot-object.png" alt="Yeni pivot nesnesi" />5. **Kaydet**'e tıklayın@@ -63,27 +63,27 @@ Bağlantı ilişkisi anahtarını etkinleştirdiğinizde, Twenty aradaki bağlan**Adlandırma kuralı**: "Project Assignment" veya "Team Membership" gibi ilişkiyi tanımlayan bir ad kullanın. Bu, veri modelinin anlaşılmasını kolaylaştırır.</Tip>-## Step 2: Create Relations Between Objects and the Junction+## Adım 2: Nesneler ile Bağlantı nesnesi arasında ilişkiler oluşturun-Add relation fields from each of your two objects to the junction object.+İki nesnenizin her birinden bağlantı nesnesine ilişki alanları ekleyin.-### First Relation (Object A → Junction)+### İlk İlişki (Nesne A → Bağlantı)-1. Select your first object in **Settings → Data Model**-2. Click **+ Add Relation**-3. Select the junction object (e.g., "Project Assignments")-4. Set the relation type to **One-To-Many** (one person can link to many assignments)+1. İlk nesnenizi **Ayarlar → Veri Modeli**'nde seçin+2. **+ İlişki Ekle**'ye tıklayın+3. Bağlantı nesnesini seçin (örn. "Project Assignments")+4. İlişki türünü **Birden-Çoğa** olarak ayarlayın (bir kişi birçok atamaya bağlanabilir)5. Alanları adlandırın:* People üzerindeki alan: örn. "Project Assignments"* Bağlantı üzerindeki alan: örn. "Person"6. **Kaydet**'e tıklayın-### Second Relation (Object B → Junction)+### İkinci İlişki (Nesne B → Bağlantı)-1. Select your second object in **Settings → Data Model**-2. Click **+ Add Relation**-3. Select the junction object (e.g., "Project Assignments")-4. Set the relation type to **One-To-Many** (one project can link to many assignments)+1. İkinci nesnenizi **Ayarlar → Veri Modeli**'nde seçin+2. **+ İlişki Ekle**'ye tıklayın+3. Bağlantı nesnesini seçin (örn. "Project Assignments")+4. İlişki türünü **Birden-Çoğa** olarak ayarlayın (bir proje birçok atamaya bağlanabilir)5. **"Bu, bir bağlantı nesnesine kurulan bir ilişkidir"** seçeneğini etkinleştirin<img src="/images/user-guide/fields/junction-relation-toggle.png" style={{width:'100%'}} />@@ -126,12 +126,12 @@ Bağlantı nesnesi hâlâ mevcuttur ve bağlantıları saklar, ancak kullanıcı### İlişkiler Ekleyin1. **People → Project Assignment**- * Type: One-to-Many+ * Tür: Birden-Çoğa* People üzerindeki alan: "Project Assignments"* Assignment üzerindeki alan: "Person"2. **Projects → Project Assignment**- * Type: One-to-Many+ * Tür: Birden-Çoğa* Projects üzerindeki alan: "Team Members"* Assignment üzerindeki alan: "Project"diff --git a/packages/twenty-docs/l/zh/developers/extend/apps/logic-functions.mdx b/packages/twenty-docs/l/zh/developers/extend/apps/logic-functions.mdxindex 75845cc8e3c..a9f1ca93b8e 100644--- a/packages/twenty-docs/l/zh/developers/extend/apps/logic-functions.mdx+++ b/packages/twenty-docs/l/zh/developers/extend/apps/logic-functions.mdx@@ -95,16 +95,16 @@ const handler = async (event: RoutePayload) => {`RoutePayload` 类型具有以下结构:- | 属性 | 类型 | 描述 | 示例 |- | ---------------------------- | ------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- |- | `headers` | `Record\<string, string \| undefined>` | HTTP 请求头(仅限 `forwardedRequestHeaders` 中列出的那些) | 见下文 |- | `queryStringParameters` | `Record\<string, string \| undefined>` | 查询字符串参数(多个值以逗号连接) | `/users?ids=1&ids=2&ids=3&name=Alice` -> `{ ids: '1,2,3', name: 'Alice' }` |- | `pathParameters` | `Record\<string, string \| undefined>` | 从路由模式中提取的路径参数 | `/users/:id`,`/users/123` -> `{ id: '123' }` |- | `body` | `object \| null` | 已解析的请求体(JSON) | `{ id: 1 }` -> `{ id: 1 }` |- | `rawBody` | `string \| undefined` | Original UTF-8 request body, before JSON parsing. Useful for verifying HMAC-style webhook signatures (e.g. GitHub's `X-Hub-Signature-256`, Stripe). `undefined` when the runtime did not preserve it. | |- | `isBase64Encoded` | `boolean` | 请求体是否为 base64 编码 | |- | `requestContext.http.method` | `string` | HTTP 方法(GET、POST、PUT、PATCH、DELETE) | |- | `requestContext.http.path` | `string` | 原始请求路径 | |+ | 属性 | 类型 | 描述 | 示例 |+ | ---------------------------- | ------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- |+ | `headers` | `Record\<string, string \| undefined>` | HTTP 请求头(仅限 `forwardedRequestHeaders` 中列出的那些) | 见下文 |+ | `queryStringParameters` | `Record\<string, string \| undefined>` | 查询字符串参数(多个值以逗号连接) | `/users?ids=1&ids=2&ids=3&name=Alice` -> `{ ids: '1,2,3', name: 'Alice' }` |+ | `pathParameters` | `Record\<string, string \| undefined>` | 从路由模式中提取的路径参数 | `/users/:id`,`/users/123` -> `{ id: '123' }` |+ | `body` | `object \| null` | 已解析的请求体(JSON) | `{ id: 1 }` -> `{ id: 1 }` |+ | `rawBody` | `string \| undefined` | 在 JSON 解析之前的原始 UTF-8 请求体。 用于验证 HMAC 风格的 Webhook 签名(例如 GitHub 的 `X-Hub-Signature-256`、Stripe)。 当运行时未保留它时为 `undefined`。 | |+ | `isBase64Encoded` | `boolean` | 请求体是否为 base64 编码 | |+ | `requestContext.http.method` | `string` | HTTP 方法(GET、POST、PUT、PATCH、DELETE) | |+ | `requestContext.http.path` | `string` | 原始请求路径 | |#### forwardedRequestHeaders