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

explain that tagging list or range of housenumbers is OK #917

Closed
matkoniecz opened this issue Feb 26, 2018 · 3 comments · Fixed by #939
Closed

explain that tagging list or range of housenumbers is OK #917

matkoniecz opened this issue Feb 26, 2018 · 3 comments · Fixed by #939

Comments

@matkoniecz
Copy link
Member

"12,14,16" or "1190-1300" are valid answers to a housenumber quest but many people are unaware about this as #910 #712 #439 and #537 indicate.

Some people ask on bug tracker but many more will never check it.

I think that idea from @rugk proposed in #910 would help

add a "Other answer" -> "There are multiple house numbers", which either pop ups a different dialog for entering, or just explains that you can tag it like that.

It would (a) reduce chance that further duplicates of #910 #712 #439 and #537 will be posted (b) will help people able to use "can't say" menu that would not check bugtracker (c) reduce response times for ones that create issues on a bug racker.

@matkoniecz matkoniecz changed the title explain that tagging list or range of housenuumbers is OK explain that tagging list or range of housenumbers is OK Feb 26, 2018
@westnordost
Copy link
Member

or just explains that you can tag it like that.

Oh yeah, that would work!

@rugk
Copy link
Contributor

rugk commented Feb 26, 2018

Some people ask on bug tracker but many more will never check it.

Correct. Never considered that, but taht's a thing to keep in mind.

@hungrymonkey
Copy link

btw, some house numbers have these 1/2 in addition to integers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants