Changeset 17038 in josm


Ignore:
Timestamp:
2020-09-18T21:11:43+02:00 (7 months ago)
Author:
Klumbumbus
Message:

fix #19805, see #17296 - Improve "Is the fixme fixed?" validator warning

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/resources/data/validator/combinations.mapcss

    r17025 r17038  
    787787
    788788/* #17296, If the value of fixme is only an osm key, it is often a leftover from a time when the object didn't have this key. The fixme was forgotten to remove when the key was added. Or the value of fixme should be described better what exactly needs to be fixed. */
    789 *[fixme][count(split(" ", tag("fixme"))) == 1][tag(tag("fixme")) != "none"],
    790 *[FIXME][count(split(" ", tag("FIXME"))) == 1][tag(tag("FIXME")) != "none"] {
     789*[fixme][count(split(" ", tag("fixme"))) == 1][has_tag_key(tag("fixme"))],
     790*[FIXME][count(split(" ", tag("FIXME"))) == 1][has_tag_key(tag("FIXME"))] {
    791791  throwWarning: tr("{0} together with {1}. Is the fixme fixed?", "{0.tag}", "{0.value}");
    792792  group: tr("suspicious tag combination");
Note: See TracChangeset for help on using the changeset viewer.