From afcd9cc3ac3031431389f70b8d898693f0888dd8 Mon Sep 17 00:00:00 2001 From: Tobias Date: Thu, 25 Apr 2024 04:42:59 +0200 Subject: [PATCH] Readme: Preset properties > `name`: Explain edge case of presets with underscore This edge case is probably due to the `stripLeadingUnderscores` in the build which removes the underscore early on in the processing. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index ce2fe40..28de2c7 100644 --- a/README.md +++ b/README.md @@ -232,7 +232,7 @@ The primary name of the feature type. Upon merging into the `main` branch, this is sent to Transifex for translating to other localizations. Changing the name of an existing preset will require it to be re-translated to all localizations. -A preset can optionally reference the label of another by using that preset's name contained in brackets, like `{preset}`. In which case the presets's _terms_ and _aliases_ are also automatically sourced from that other field. This is for example useful for regional presets which should get the same labels as the preset they are based on. +A preset can optionally reference the label of another by using that preset's name contained in brackets, like `{presetId}` or `{folder/presetId}`. In which case the presets's _terms_ and _aliases_ are also automatically sourced from that other field. This is for example useful for regional presets which should get the same labels as the preset they are based on. The `presetId` is the same as the filename but ignoring the underscore convention for unsearchable presets. So for a preset at `folder/_name` the reference would be `{folder/name}`. This property is required. There is no default.