#10329 closed enhancement (fixed)
give warning for color=*
Reported by: | Klumbumbus | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | 15.04 |
Component: | Core validator | Version: | |
Keywords: | color, colour | Cc: |
Description
JOSM validator should warn about color=* since colour=* is the correct key.
see
Attachments (1)
Change History (23)
comment:1 by , 10 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
comment:3 by , 10 years ago
Data correction - is it applied to all objects or just modified ones? In the second case validator test still would be useful.
follow-up: 5 comment:4 by , 10 years ago
color
is not delete if colour
with the same value does already exist.
comment:5 by , 10 years ago
Replying to skyper:
color
is not delete ifcolour
with the same value does already exist.
Is it possible to delete it silently in this case ?
follow-up: 8 comment:6 by , 10 years ago
Milestone: | → 15.04 |
---|---|
Resolution: | worksforme |
Status: | closed → reopened |
The situation around color
is not satisfying.
- If you add
color
it silently addscolour
on upload but keepscolor
. - If you modify and upload an object with value of color = value of colour nothing happens.
- No warnings if you manually run the validator.
comment:7 by , 10 years ago
Also I would not use a silent autofix for color, since the user does not learn from his mistakes.
follow-up: 9 comment:8 by , 10 years ago
Replying to Klumbumbus:
The situation around
color
is not satisfying.
- If you add
color
it silently addscolour
on upload but keepscolor
.
That should not be the case. color is changed into colour, not added.
- If you modify and upload an object with value of color = value of colour nothing happens.
- No warnings if you manually run the validator.
You can add proper validator warnings. The silent change is there, as this is an error we introduced with JOSM presets.
comment:9 by , 10 years ago
Replying to stoecker:
Replying to Klumbumbus:
The situation around
color
is not satisfying.
- If you add
color
it silently addscolour
on upload but keepscolor
.That should not be the case. color is changed into colour, not added.
Happend to me, that I added color
, the upload seemed fine and the result is http://www.openstreetmap.org/way/203410463.
Thanks to Osmose I noticed this.
comment:14 by , 10 years ago
Don't see that this may have caused the problem. I think the issue is there from the very beginning.
comment:16 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
comment:17 by , 10 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
If you change and try to upload an object with colour=red
and color=red
, then first the validator warning appears and then the autoremove applies. The same if you add a new object with color
. Can this be changed, so first the autofixes take place and then the validator runs? This way the validator warnings will not appear, because the autofix repairs it before.
comment:18 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
Your change would bring previous state back. Silent change without warning. Can be simply reached by removing the checks :-)
I think current way is right. User gets warned and can fix it. If he does not, the silent changes kick in.
comment:19 by , 10 years ago
The difference would be that you get warnings when running the validator manually on the whole data set, not only modified objects on upload. However we can keep the current situation.
comment:20 by , 10 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
There exist some combinations with color
see taginfo and my example file.
Can we have a warning about any color:
, :color
and :color:
. Thanks.
We already have an automatic correction on upload, I don't think this is worth a new manual test: