Incomplete role elements in preset for hiking routes

[simon@…]

The entry for hiking routes contains the following role elements

<role key="" text="route segment" requisite="required" type="way,closedway" member_expression="highway|route=ferry"/>
<role key="" text="infrastructure" requisite="optional" type="node,closedway" member_expression="tourism OR amenity"/>
<role key="" text="natural" requisite="optional" type="node,closedway" member_expression="natural=peak OR natural=volcano OR mountain_pass=yes OR natural=water OR tourism=viewpoint OR amenity=drinking_water OR natural=spring OR place=locality"/>

IMHO this does not make a lot of sense either there are role keys for the members or there aren't and then likely the role entries should be dropped.

[stoecker]

I don't understand what you want?

[Don-vip]

For reference, this has been added in r6810 to fix #9586

[Klumbumbus]

Do you mean that the role column in the table in the preset window is empty?

[Klumbumbus]

I think I understand now what he means: remove key="" because it is a bit superflous and can be assumed as default if no key is set in the preset code. (however according to TaggingPresets key is a required attribute)