Modify ↓
#11389 closed enhancement (fixed)
[Patch] Check for maxspeed in combination with maxspeed:forward/backward
Reported by: | Basstoelpel | Owned by: | Basstoelpel |
---|---|---|---|
Priority: | normal | Milestone: | 15.09 |
Component: | Core validator | Version: | latest |
Keywords: | validator maxspeed | Cc: |
Description
Validator should check for the combination of maxspeed and maxspeed:forward or maxspeed:backward. Either the combination is superfluous or inconsistent.
And maybe it should check for equal values in maxspeed:forward and maxspeed:backward, because that can be simplified.
Attachments (1)
Change History (8)
by , 9 years ago
Attachment: | validate-maxspeed.patch added |
---|
comment:1 by , 9 years ago
comment:2 by , 9 years ago
Summary: | Check for maxspeed in combination with maxspeed:forward/backward → [Patch] Check for maxspeed in combination with maxspeed:forward/backward |
---|
comment:5 by , 9 years ago
Milestone: | 15.08 → 15.09 |
---|---|
Owner: | changed from | to
Status: | new → needinfo |
Thanks for the patch. Like for #11529, can you please see if the test can be converted to a MapCSS-based one instead?
Note:
See TracTickets
for help on using tickets.
This patch validates the "maxspeed", "maxspeed:backward", "maxspeed:forward", "source:maxspeed" and "zone:maxspeed" values.
If "maxspeed:backward" and "maxspeed:forward" have the same value, a warning message suggests to use the "maxspeed" tag instead.