Opened 3 years ago

Closed 3 years ago

Last modified 2 years ago

#20022 closed defect (fixed)

Do not warn about destination_sign relations with same members

Reported by: skyper Owned by: GerdP
Priority: normal Milestone: 20.11
Component: Core validator Version:
Keywords: template_report destination_sign relation same member Cc:


What steps will reproduce the problem?

  1. Have two destination_sign relations with identical members but different tags
  2. Run validator

What is the expected result?

No warning

What happens instead?

Warning: Relations with same members (1)

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

As written on the wiki page below the tags table relations with same members should be created if you want to add detailed information for each destination.

Please, exclude, type=destination_sign from this test, thanks a lot.

Relative:URL: ^/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2020-10-31 01:21:14 +0100 (Sat, 31 Oct 2020)
Build-Date:2020-10-31 02:30:50

Attachments (0)

Change History (5)

comment:1 Changed 3 years ago by GerdP

Owner: changed from team to GerdP
Status: newassigned

comment:2 Changed 3 years ago by GerdP

Resolution: fixed
Status: assignedclosed

In 17326/josm:

fix #20022: Do not warn about destination_sign relations with same members

  • ignore type=destination_sign

comment:3 Changed 3 years ago by GerdP

Milestone: 20.10

comment:4 Changed 3 years ago by Don-vip

Milestone: 20.1020.11

Milestone renamed

comment:5 Changed 2 years ago by skyper

With #20425 and r17476 in #20293 in mind, it might be better to remove the ignored type=* for now.

A destination_sign relation with same members and same tags but different value for distance is still an error.

Modify Ticket

Change Properties
Set your email in Preferences
as closed The owner will remain GerdP.
as The resolution will be set.
The resolution will be deleted.

Add Comment

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

Note: See TracTickets for help on using tickets.