cli config list docs: explain config key format in templates

This also means that this field should not become a `List<String>`,
though it would make sense to create a new type for it (which could be
converted into `List<String>` in two different ways, with or without
quoting).
This commit is contained in:
Ilya Grigoriev 2025-12-21 23:39:02 -08:00 committed by Ilya Grigoriev
parent 513c5f7b3c
commit b2792e190b
2 changed files with 6 additions and 2 deletions

View file

@ -49,7 +49,7 @@ pub struct ConfigListArgs {
///
/// The following keywords are available in the template expression:
///
/// * `name: String`: Config name.
/// * `name: String`: Config name, in [TOML's "dotted key" format].
/// * `value: ConfigValue`: Value to be formatted in TOML syntax.
/// * `overridden: Boolean`: True if the value is shadowed by other.
/// * `source: String`: Source of the value.
@ -61,6 +61,8 @@ pub struct ConfigListArgs {
///
/// See [`jj help -k templates`] for more information.
///
/// [TOML's "dotted key" format]: https://toml.io/en/v1.0.0#keys
///
/// [`jj help -k templates`]:
/// https://docs.jj-vcs.dev/latest/templates/
#[arg(

View file

@ -731,7 +731,7 @@ List variables set in config files, along with their values
The following keywords are available in the template expression:
* `name: String`: Config name.
* `name: String`: Config name, in [TOML's "dotted key" format].
* `value: ConfigValue`: Value to be formatted in TOML syntax.
* `overridden: Boolean`: True if the value is shadowed by other.
* `source: String`: Source of the value.
@ -743,6 +743,8 @@ List variables set in config files, along with their values
See [`jj help -k templates`] for more information.
[TOML's "dotted key" format]: https://toml.io/en/v1.0.0#keys
[`jj help -k templates`]:
https://docs.jj-vcs.dev/latest/templates/