Modify

Opened 11 years ago

Closed 11 years ago

#9517 closed defect (fixed)

Some issues with the MapCSS validator when reloading config file

Reported by: naoliv Owned by: team
Priority: normal Milestone: 14.01
Component: Core validator Version:
Keywords: Cc:

Description (last modified by naoliv)

Include this example mapcss file:

*[name = *ref][highway] {
        throwWarning: tr("{0} and {1} are the same", "{0.key}", "{0.value}");
}

and validate one highway where the name = ref. You correctly get the validation result (saying that both are the same).

With JOSM still open (and after running the validation), edit the mapcss file and change to something like this (only the message was changed):

*[name = *ref][highway] {
        throwWarning: tr("please, fix {0} and {1}", "{0.key}", "{0.value}");
}

Go to edit, preferences, data validator, click on the local mapcss file, edit and OK (just to reload the mapcss file).
Then validate it one more time.
Note how now we have both messages: one with the old text and another with the current one.

Second problem: still with this test session, do the step above to reload the mapcss one more time (without changing anything) and then validate the data again. Now we have a duplicated message saying to fix the name and the ref.
Everytime that the mapcss file is reload the tests result get duplicated.

Attachments (0)

Change History (3)

comment:1 by naoliv, 11 years ago

Description: modified (diff)

comment:2 by Don-vip, 11 years ago

Milestone: 14.01
Summary: Some issues with the MapCSS validatorSome issues with the MapCSS validator when reloading config file

comment:3 by simon04, 11 years ago

Resolution: fixed
Status: newclosed

In 6612/josm:

fix #9517 - Some issues with the MapCSS validator when reloading config file

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain team.
as The resolution will be set.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.