Reformat the config file documentation format of DM, Lightning, TiCDC, TiFlash to the same as that of TiDB, TiKV, PD, TiProxy #19005
Labels
area/dm
area/ticdc
Indicates that the Issue or PR belongs to the area of TiCDC.
area/tidb-lightning
Indicates that the Issue or PR belongs to the area of TiDB Lightning.
type/enhancement
The issue or PR belongs to an enhancement.
Change Request
Please answer the following questions before submitting your issue. Thanks!
The config doc of DM, Lightning, CDC and TiFlash mostly just the config template verbatim. The explanation of each config is either laid out as a table, or worse, as inline TOML/YAML comments. The problems are
These documentation should align with the format chosen by TiDB, TiKV and PD etc, using one
<h3>
section for each config item and one<h2>
for each group.The content of each config item can show the default value, possible ranges. Each item can have the "New in vX.Y" showing the supported version range. The description itself can be formatted and link to other documentations (unlike inline comments). Caveats can be explained in details without worrying about
<td>
size.Config documentation which I consider bad:
Config documentation which are better:
The text was updated successfully, but these errors were encountered: