Changes between Version 185 and Version 186 of TaggingPresets

Timestamp:

2021-06-23T18:38:28+02:00 (4 years ago)

Author:

skyper

Comment:

add tickets about problems with "match_expression" and "value_template"

TaggingPresets

@@ -187 +187 @@
  match_expression="search expression"::
    additional criteria for matching primitives, specified in [wikitr:/Help/Action/Search JOSM search] syntax. ''(since r17662)'' \\
-   For instance, a preset with `match_expression="foo=bar"` requires OSM objects to have the tag `foo=bar`. You may want to use the `match_expression=""` to exclude certain OSM objects, e.g. when a more specific preset is present.
+   For instance, a preset with `match_expression="foo=bar"` requires OSM objects to have the tag `foo=bar`. You may want to use the `match_expression=""` to exclude certain OSM objects, e.g. when a more specific preset is present. \\
+  **Note**: Does not work, yet, see #20843.
  id="unique_identifier"::
    the unique identifier for this `<chunk>`
@@ -223 +224 @@
  value_template="template"::
    A template to generate the value automatically based on other tag values of the object. The syntax of `name_template=""` is used, [#NameTemplateSyntax see below]. ''(since r17639)'' \\
-   For instance, `"Bus {ref}: {from} → {to}"` can be used to generate the name of a bus route relation.
+   For instance, `"Bus {ref}: {from} → {to}"` can be used to generate the name of a bus route relation. \\
+  **Note**: There are some minor problems with this attribute, see #20851 and #20861.
 \\