Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When object has NSI entry, tag fix is displayed as brand fix #10672

Open
danieldegroot2 opened this issue Jan 10, 2025 · 4 comments
Open

When object has NSI entry, tag fix is displayed as brand fix #10672

danieldegroot2 opened this issue Jan 10, 2025 · 4 comments
Labels
bug A bug - let's fix this! validation An issue with the validation or Q/A code

Comments

@danieldegroot2
Copy link
Contributor

URL

No response

How to reproduce the issue?

When editing an object with an NSI entry, tag fix/upgrade/suggestion warnings are shown as non-standard brand warnings.
This happens even when the corresponding tags are already present and there are no other/new tags to change.
In the first case it could be useful to separate the outdated tag fix to avoid slightly confusing change to non-brand tag.
In the last case, it should be shown as i.e. 'outdated tags' as usual.

Steps to reproduce

  1. Add new node
  2. Add i.e. amenity=charging_station + name=EasyGo => 'non-standard brand`
  3. Accept brand suggestion
  4. Add survey_date=2023 => displays tag change as 'non-standard brand' change, while it is only `outdated tag' change.

Screenshot(s) or anything else?

https://www.openstreetmap.org/node/11001736756

Observed
With brand suggestion (when only amenity=charging_station + name=EasyGo is added)
image

With only the outdated tag suggestion remaining (when brand tags are already added)
image

Expected for last case (when brand tags are already added)
image

Which deployed environments do you see the issue in?

Released version at openstreetmap.org/edit, Development version at ideditor.netlify.app, RapiD version at mapwith.ai/rapid

What version numbers does this issue effect?

2.30.4, 2.31.0-dev, Rapid 2.5.0

Which browsers are you seeing this problem on?

Chrome

@Avan2021

This comment was marked as off-topic.

@tyrasd tyrasd added bug A bug - let's fix this! validation An issue with the validation or Q/A code labels Jan 14, 2025
@tyrasd
Copy link
Member

tyrasd commented Jan 14, 2025

I can confirm this bug… There seems to be some unwanted interaction between the NSI matching and deprecated tag replacement validations. However I would not consider it as a critical bug, as the other warning is also not completely off (at least in English).

@Avan2021
Copy link

Since you confirmed this bug, can I work on this and if I make a pr, will it considered?

@tyrasd
Copy link
Member

tyrasd commented Jan 15, 2025

@Avan2021 As this bug is touching relatively complex parts of the code, I don't necessarily think it is a good first issue to tackle for a beginner like you. If you however find a proper solution it will of course be considered.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A bug - let's fix this! validation An issue with the validation or Q/A code
Projects
None yet
Development

No branches or pull requests

3 participants