-
Notifications
You must be signed in to change notification settings - Fork 62
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
Rephrase note_body to make some keys copyable #99
Open
JesseWeinstein
wants to merge
1
commit into
osmlab:gh-pages
Choose a base branch
from
JesseWeinstein:patch-1
base: gh-pages
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
By the way, this field probably requires the reviewer’s attention too, because the country and area code may be missing: #94. That said, phone numbers needing additional formatting are quite common in OSM anyways.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, there are a bunch of formatting adjustments that ideally would be done in the onosm code at the time the data was submitted -- things like: "Did you forget the area code?" and converting
@blahblah
into "https://twitter.com/blahblah". But as you said, mis-formatted values are pretty common, so it seemed safe enough to allow for copy/paste for them.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is why I have generally been opposed to direct "copy paste" support. The values are almost never directly pastable, and I don't want to encourage adding bad data to OSM. If a mapper doesn't want to take the time to research a submission from onosm with first-hand data, they should leave it as-is and move on.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The name value is nearly always copy-pastable, as is the website, and in most cases, the twitter and facebook. Researching is certainly needed, but not to replace these values, but to confirm the existence and location of the business. And people will still copy paste even if you use colons rather than equals signs, it'll just add a bit of extra work for no purpose.