-
Notifications
You must be signed in to change notification settings - Fork 911
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
Update to iD v2.21.0 #3561
Update to iD v2.21.0 #3561
Conversation
major changes in this release: * dropped support for Internet Explorer 11 * switched authentication to OAuth 2 for further changes please refer to https://github.com/openstreetmap/iD/blob/release/CHANGELOG.md#2210
* 'Modify the map' | ||
* 'Read private GPS traces' | ||
* 'Upload GPS traces' | ||
* 'Modify notes' |
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.
Does it actually need the two new permissions that it didn't have before?
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.
In 2.21.0, iD requests the write_prefs
scope (see https://github.com/openstreetmap/iD/blob/v2.21.0/modules/services/osm.js#L23). AFAICS it is not (yet) used anywhere obvious. (//cc @bhousel: Did I overlooking something here?) I was however planning to make use of it in the not so far future to preserve some settings and/or editor states. That's why I choose to just keep it in.
write_gpx
is currently not used by iD (and also not requested during authentication), but I thought about adding a functionality to upload traces from within iD at some point in the future.
I assumed that for a typical user setting up this repo, it would be less trouble to allow all potentially/eventually used permissions right now, as this would prevent hard to debug issues when the scopes would be used by iD at some point in the future.
Let me know if you prefer to handle it differently. I can also prepare a patch release which doesn't request write_prefs
.
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.
I'm happy to add them. I was just trying to check what was going on so I knew what to do when creating applications for production.
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.
AFAICS it is not (yet) used anywhere obvious. (//cc @bhousel: Did I overlooking something here?) I was however planning to make use of it in the not so far future to preserve some settings and/or editor states. That's why I choose to just keep it in.
Yes write_prefs
is not used currently, but it's been something we've considering for a long time and might use eventually: openstreetmap/iD#3002
There was no need to create IDs on the dev and production servers - the operations team will take care of that. |
Ok. I had created those IDs for the non-integrated standalone version(s) of iD (e.g. ideditor.netlify.app/) already (see https://github.com/openstreetmap/iD/blob/v2.21.0/index.html#L46-L54). Do you prefer that I replace these with IDs/secrets provided by the operations team as well or is it fine to keep them as is? |
I know nothing about that but I'd say do whatever you've been doing which I guess is having your own ID for it. I was just saying that I'll create an application on the production site for deployment, and dev is actually done automatically by chef. |
that works for me. |
The following major changes required some adaptions of the iD integration code in this repo:
Vendorfile
– use non-legacy source file for iD (which works in modern browsers, but not IE11)CONFIGURE.md
&config/settings.yml
– updated the installation instructions.app/assets/javascripts/edit/id.js.erb
&app/views/site/_id.html.erb
– simplify the check whether iD is configuredapp/assets/javascripts/id.js
&app/views/site/id.html.erb
– upgrade to OAuth 2 authenticationtest/controllers/site_controller_test.rb
– remove some unnecessary setup/cleanup codeFor the main iD deployments on osm.org, I've created new OAuth 2 Client IDs:Ee1wWJ6UlpERbF6BfTNOpwn0R8k_06mvMXdDUkeHMgw
(for api06.dev.osm.org) and0tmNTmd0Jo1dQp4AUmMBLtGiD9YpMuXzHefitcuVStc
(for osm.org).Further changes from the changelog:
✅ Validation
🐛 Bugfixes
public_transport=platform
,waterway=dam
orhighway=elevator
as areas (#8985)🚀 Presets
access
fields (#8945)vehicle
tag as placeholder value ofaccess
fields formotor_vehicle
andbicycle
golf
featurestee
,fairway
,rough
andgreen
in green color and using a grass pattern (#8927)*=no
tags by a preset'saddTags
access=no
in access field ofhighway=construction
objects (#9102)aliases
(#6139)key=value
) (#8869)Other
🔨 Development
v7.1
,fontawesome
tov6.1
,d3
tov7.4
,node-diff
tov3.1
,mocha
tov9.2
,svg-sprite
tov1.5.4
,marked
tov4.0
,temaki
tov5.1
,mapillary-js
tov4.1