﻿id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
19190	Option to set and call variables in tagging presets and validator rules	skyper	team	"I often find myself ''copy & pasting'' value strings which are identical in presets.
An option to define that string in a variable and call it later would make life much easier, especially, when updating values and in terms of consistency.


{{{
#!preset
    <combo key=""turn:lanes:forward"" text=""Turn lanes in way direction"" values=""left|left,left|through,left;through|through,left;through|through;right,left|through;right,left;through|right,through|through,through|through;right,through|right,right|right,none|right,left|none,left|through|right,left|through|through;right,left;through|through|right,left;through|through;right|right,left|left;through|through|right,left|through|through;right|right,left|through|through|right,merge_to_right|merge_to_left,none|merge_to_left,merge_to_right|none,reverse|sharp_left;left|slight_left|through|slight_right;right|sharp_right|none"" values_searchable=""true"" values_sort=""false"" match=""key"" />
    <combo key=""turn:lanes:backward"" text=""Turn lanes opposed to way direction"" values=""left|left,left|through,left;through|through,left;through|through;right,left|through;right,left;through|right,through|through,through|through;right,through|right,right|right,none|right,left|none,left|through|right,left|through|through;right,left;through|through|right,left;through|through;right|right,left|left;through|through|right,left|through|through;right|right,left|through|through|right,merge_to_right|merge_to_left,none|merge_to_left,merge_to_right|none,reverse|sharp_left;left|slight_left|through|slight_right;right|sharp_right|none"" values_searchable=""true"" values_sort=""false"" match=""key"" />
}}}

Would change to:

{{{
#!preset
<var name=""turnlane"" value=""left|left,left|through,left;through|through,left;through|through;right,left|through;right,left;through|right,through|through,through|through;right,through|right,right|right,none|right,left|none,left|through|right,left|through|through;right,left;through|through|right,left;through|through;right|right,left|left;through|through|right,left|through|through;right|right,left|through|through|right,merge_to_right|merge_to_left,none|merge_to_left,merge_to_right|none,reverse|sharp_left;left|slight_left|through|slight_right;right|sharp_right|none"" />

    <combo key=""turn:lanes:forward"" text=""Turn lanes in way direction"" values=""match_var(turnlane)"" values_searchable=""true"" values_sort=""false"" match=""key"" />
    <combo key=""turn:lanes:backward"" text=""Turn lanes opposed to way direction"" values=""match_var(turnlane)"" values_searchable=""true"" values_sort=""false"" match=""key"" />
}}}

Similar is true for, e.g., long regex in validator rules. Again, a variable could solve the problem."	enhancement	new	normal		Core			variable tagging preset rule	
