lxcxjxhx opened a new pull request, #13123:
URL: https://github.com/apache/seatunnel/pull/13123
### What
`docs/en/introduction/concepts/connector-v2-features.md` declares `###
multimodal` twice — once under **Source Connector Features**, once under **Sink
Connector Features**. Both slugify to `#multimodal`, and 23 pages link to
`connector-v2-features.md#multimodal`:
- 12 source connectors → should land on the source section ✔
- 11 sink connectors → should land on the sink section ✘
GitHub resolves a duplicated anchor to the **first** occurrence, so every
sink page's `[x] [multimodal]` checkbox currently opens the *source*
description instead of the sink one.
### Fix
The file already distinguishes the read/write pair for tables (`support
multiple table read` / `support multiple table write`), so the sink section
follows the same pattern:
```diff
### multimodal
Support multimodal data integration, including structured and unstructured
text data, video, images, binary files, etc.
### support multiple table write
...
### multimodal
+### multimodal write
```
and the 11 sink connector pages now point at `#multimodal-write`.
### How the defect was found / verified
Ambiguous in-page links in `docs/en` (link target file has two or more
headings with the same slug):
```
before: 50 after: 2
```
The two remaining ones are out of scope here and deliberately untouched:
`Paimon.md` and `Elasticsearch.md` both have `## Schema Evolution` plus `###
Schema evolution` inside `## Examples`, and the links from
`introduction/configuration/schema-evolution.md` resolve to the narrative
section — accidentally correct, so renaming would only churn anchors for no
behaviour change.
`anchor_check` on the whole `docs/en` tree: `files=555 bad-anchors=0` — the
new `#multimodal-write` target resolves, and the 12 source links still resolve
to the source section.
### Checks run
- 12 files, 12 insertions, 12 deletions — no content changed, only heading
name and link targets.
- `docs/zh` untouched: the zh feature page has the same duplicate heading
but no connector page links to it, so there is nothing broken to fix there.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]