Opened 4 weeks ago

Last modified 3 weeks ago

#19519 new defect

property value for multiselect always produce false positive with multiple values

Reported by: skyper Owned by: team
Priority: normal Milestone:
Component: Core validator Version:
Keywords: template_report multiselect property value Cc:


What steps will reproduce the problem?

  1. Have a tag with <multiselect /> in preset
  2. add multiple values
  3. run validator

What is the expected result?

No informal warning

What happens instead?

Presets do not contain property value

Please provide any additional information below. Attach a screenshot if possible.

For <multiselect >/ the whole list needs to be taken into account.

Relative:URL: ^/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2020-07-09 17:42:41 +0200 (Thu, 09 Jul 2020)
Build-Date:2020-07-10 01:30:51

Attachments (0)

Change History (2)

comment:1 Changed 3 weeks ago by simon04

In 16788/josm:

see #19519 - TagCheckerTest: add mon-regression test

comment:2 Changed 3 weeks ago by simon04

Possible fix: split multiple values before testing (using OsmUtils#splitMultipleValues)

Modify Ticket

Change Properties
Set your email in Preferences
as new The owner will remain team.
as The resolution will be set.
to The owner will be changed from team to the specified user.
The owner will change to skyper
as duplicate The resolution will be set to duplicate.The specified ticket will be cross-referenced with this ticket
The owner will be changed from team to anonymous.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.