From f3318ac8311e08fa82d3518fccc2dbf54c44634d Mon Sep 17 00:00:00 2001 From: Nikita Date: Mon, 3 Aug 2026 23:31:02 +0200 Subject: [PATCH] fix(extend): render the config-file mapping headings, repair their anchors MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Twelve headings on the Configuration File page still carried kramdown's `---` em-dash shorthand ("Input mapping --- basic"). Kramdown turned that into an em dash and slugged the id off the result; Starlight renders the three hyphens literally and slugs them too, so the page showed "Input mapping --- basic" and the ids became `input-mapping-----basic`. Using a real em dash fixes both at once: the heading reads correctly and the id goes back to the kramdown-era `input-mapping--basic`, so anchor links written against developers.keboola.com — including the ones in component repos we cannot edit — resolve again. Two links were pointing at a third spelling, `#output-mapping---delete-rows`, which never existed on either site; they now match the built id. Verified against the build (`astro build`): all 12 ids are the `--` form, and every in-repo link to a config-file anchor resolves. audit-phase2 unchanged at 45 broken internal links / 0 missing images / 3 multi-h1. Co-Authored-By: Claude Opus 5 --- .../common-interface/config-file/index.md | 24 +++++++++---------- .../index.md | 2 +- .../out-tables-manifests/index.md | 2 +- 3 files changed, 14 insertions(+), 14 deletions(-) diff --git a/src/content/docs/extend/common-interface/config-file/index.md b/src/content/docs/extend/common-interface/config-file/index.md index 3867f2452..ad50d2227 100644 --- a/src/content/docs/extend/common-interface/config-file/index.md +++ b/src/content/docs/extend/common-interface/config-file/index.md @@ -305,7 +305,7 @@ The tables element in a configuration of the **output mapping** is an array and - `enclosure` - `write_always` -#### Input mapping --- basic +#### Input mapping — basic Download tables `in.c-ex-salesforce.Leads` and `in.c-ex-salesforce.Accounts` to `/data/tables/in/leads.csv` and `/data/tables/in/accounts.csv`. @@ -351,7 +351,7 @@ In an API request, this would be passed as: } ``` -#### Input mapping --- incremental load +#### Input mapping — incremental load Download 2 days of data from the `in.c-storage.StoredData` table to `/data/tables/in/in.c-storage.StoredData`. ```json @@ -369,7 +369,7 @@ Download 2 days of data from the `in.c-storage.StoredData` table to `/data/table } ``` -#### Input mapping --- select columns +#### Input mapping — select columns ```json { @@ -386,7 +386,7 @@ Download 2 days of data from the `in.c-storage.StoredData` table to `/data/table } ``` -#### Input mapping --- column types +#### Input mapping — column types This is applicable only to [workspace mapping](/extend/common-interface/folders/#exchanging-data-via-workspace), for CSV files this setting has no effect. The `column_types` setting maps to [Storage API load options](https://api.keboola.com/?service=storage#post-/v2/storage/branch/-branchId-/workspaces/-workspaceId-/load). It also acts the same way as `columns` setting allowing you to limit the table columns. If both `column_types` and `columns` setting are used, then the listed columns must match. If you omit `columns` and use only `column_types` (recommended) then `columns` will be propagated automatically from `column_types`. @@ -414,7 +414,7 @@ If both `column_types` and `columns` setting are used, then the listed columns m } ``` -#### Input mapping --- filtered table +#### Input mapping — filtered table ```json { @@ -434,7 +434,7 @@ If both `column_types` and `columns` setting are used, then the listed columns m } ``` -#### Output mapping --- basic +#### Output mapping — basic Upload `/data/out/tables/out.c-main.data.csv` to `out.c-main.data`. ```json @@ -452,7 +452,7 @@ Upload `/data/out/tables/out.c-main.data.csv` to `out.c-main.data`. } ``` -#### Output mapping --- headless CSV +#### Output mapping — headless CSV Upload `/data/out/tables/data.csv`, a CSV file without headers on its first line, to the table `out.c-main.data`. ```json @@ -471,7 +471,7 @@ Upload `/data/out/tables/data.csv`, a CSV file without headers on its first line } ``` -#### Output mapping --- set additional properties +#### Output mapping — set additional properties Incrementally upload `/data/out/tables/data.csv` to `out.c-main.data` with a compound primary key set on the columns `column1` and `column2`. @@ -492,7 +492,7 @@ with a compound primary key set on the columns `column1` and `column2`. } ``` -#### Output mapping --- write even if the job fails +#### Output mapping — write even if the job fails If you have a table that you are updating during the execution of the job and you want to output that table even if the job fails then you can use the `write_always` flag @@ -512,7 +512,7 @@ and you want to output that table even if the job fails then you can use the `wr } ``` -#### Output mapping --- delete rows +#### Output mapping — delete rows Delete data from the `destination` table before uploading the CSV file (only makes sense with `incremental: true`). The `delete_where` parameter provides a flexible way to specify which records should be deleted from the target table before loading new data into it. It supports time-based filters and multiple filter conditions: @@ -740,7 +740,7 @@ All files matching the search will be downloaded to the `/data/in/files` folder. The name of each file has the `fileId_fileName` format. Each file will also contain a [manifest](/extend/common-interface/manifest-files/) with all information about the file. -#### Input mapping --- query +#### Input mapping — query ```json { @@ -765,7 +765,7 @@ This will download with files with matching `.zip` **and** having the `docker-de /data/in/files/75807657_fooBarBaz.zip /data/in/files/75807657_fooBarBaz.zip.manifest -#### Output mapping --- basic +#### Output mapping — basic Define additional properties for uploaded files in the output mapping configuration. If that file is not present in the `/data/out/files` folder, an error will be thrown. diff --git a/src/content/docs/extend/common-interface/manifest-files/out-tables-manifests-native-types/index.md b/src/content/docs/extend/common-interface/manifest-files/out-tables-manifests-native-types/index.md index 4968ea1fb..852dddf73 100644 --- a/src/content/docs/extend/common-interface/manifest-files/out-tables-manifests-native-types/index.md +++ b/src/content/docs/extend/common-interface/manifest-files/out-tables-manifests-native-types/index.md @@ -46,7 +46,7 @@ filled by the Id of the running component (e.g., `keboola.ex-db-snowflake`). ``` Additionally, the following options will cause the specified rows to be deleted from the source table before the new -table is imported. See an [example](/extend/common-interface/config-file/#output-mapping---delete-rows). +table is imported. See an [example](/extend/common-interface/config-file/#output-mapping--delete-rows). Using this option makes sense only with [incremental loads](/components/extractors/generic-extractor/incremental/). ```json diff --git a/src/content/docs/extend/common-interface/manifest-files/out-tables-manifests/index.md b/src/content/docs/extend/common-interface/manifest-files/out-tables-manifests/index.md index 80319e225..0638e5973 100644 --- a/src/content/docs/extend/common-interface/manifest-files/out-tables-manifests/index.md +++ b/src/content/docs/extend/common-interface/manifest-files/out-tables-manifests/index.md @@ -43,7 +43,7 @@ Additionally, the following options can be specified: ``` The options will cause the specified rows to be deleted from the source table before the new -table is imported. See an [example](/extend/common-interface/config-file/#output-mapping---delete-rows). +table is imported. See an [example](/extend/common-interface/config-file/#output-mapping--delete-rows). Using this option makes sense only with [incremental loads](/components/extractors/generic-extractor/incremental/). The `metadata` and `column_metadata` fields allow you to set