Skip to content

Conversation

@hanbyul-here
Copy link
Contributor

@hanbyul-here hanbyul-here commented Jan 2, 2018

  • added shutdown notice
  • @louh can I ask you to review, merge and release?

@louh
Copy link
Contributor

louh commented Jan 4, 2018

@hanbyul-here good idea. I'd like to suggest that we do this warning where the other warnings are made: https://github.com/mapzen/leaflet-geocoder/blob/master/src/core.js#L93 - and check to see if the url option is either not provided or contains a search.mapzen.com hostname.

It might also be a good idea to include a link to look for alternatives at the Pelias project: http://pelias.io/

@coveralls
Copy link

Coverage Status

Coverage decreased (-56.3%) to 11.531% when pulling 1636c3c on hanb/shutdown-warning into 834ae4e on master.

src/core.js Outdated
// Make sure people aware of Mapzen hosted services are going down.
var mapzenHostedServiceUrl = 'https://search.mapzen.com';

if (options.url.indexOf(mapzenHostedServiceUrl)) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will fail if options or options.url is undefined.

The other warnings will check to make sure options is defined (e.g. someone has actually specified options). It should also throw the warning if options.url isn't set, because it would then default to Mapzen Search.

Copy link
Contributor Author

@hanbyul-here hanbyul-here Jan 4, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do you mind if I do check against this.options.url directly after default options were merged with users'? It seems to make more sense to check the final url set for this case.

Copy link
Contributor

@louh louh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See comment

@louh
Copy link
Contributor

louh commented Jan 4, 2018 via email

@coveralls
Copy link

Coverage Status

Coverage increased (+0.6%) to 68.371% when pulling 40e773c on hanb/shutdown-warning into 834ae4e on master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.6%) to 68.371% when pulling 40e773c on hanb/shutdown-warning into 834ae4e on master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.6%) to 68.371% when pulling 40e773c on hanb/shutdown-warning into 834ae4e on master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.6%) to 68.371% when pulling 40e773c on hanb/shutdown-warning into 834ae4e on master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.6%) to 68.371% when pulling 40e773c on hanb/shutdown-warning into 834ae4e on master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.6%) to 68.371% when pulling 40e773c on hanb/shutdown-warning into 834ae4e on master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.6%) to 68.371% when pulling 40e773c on hanb/shutdown-warning into 834ae4e on master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.6%) to 68.371% when pulling 40e773c on hanb/shutdown-warning into 834ae4e on master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.6%) to 68.371% when pulling 40e773c on hanb/shutdown-warning into 834ae4e on master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.6%) to 68.371% when pulling 40e773c on hanb/shutdown-warning into 834ae4e on master.

@coveralls
Copy link

Coverage Status

Coverage increased (+1.1%) to 68.939% when pulling ac4e741 on hanb/shutdown-warning into 834ae4e on master.

@coveralls
Copy link

Coverage Status

Coverage increased (+1.1%) to 68.939% when pulling ac4e741 on hanb/shutdown-warning into 834ae4e on master.

@coveralls
Copy link

Coverage Status

Coverage increased (+1.1%) to 68.939% when pulling ac4e741 on hanb/shutdown-warning into 834ae4e on master.

@coveralls
Copy link

Coverage Status

Coverage increased (+1.1%) to 68.939% when pulling ac4e741 on hanb/shutdown-warning into 834ae4e on master.

@coveralls
Copy link

Coverage Status

Coverage increased (+1.1%) to 68.939% when pulling ac4e741 on hanb/shutdown-warning into 834ae4e on master.

@coveralls
Copy link

Coverage Status

Coverage increased (+1.1%) to 68.939% when pulling ac4e741 on hanb/shutdown-warning into 834ae4e on master.

@coveralls
Copy link

Coverage Status

Coverage increased (+1.1%) to 68.939% when pulling ac4e741 on hanb/shutdown-warning into 834ae4e on master.

@coveralls
Copy link

Coverage Status

Coverage increased (+1.1%) to 68.939% when pulling ac4e741 on hanb/shutdown-warning into 834ae4e on master.

@coveralls
Copy link

Coverage Status

Coverage increased (+1.1%) to 68.939% when pulling ac4e741 on hanb/shutdown-warning into 834ae4e on master.

@coveralls
Copy link

Coverage Status

Coverage increased (+1.1%) to 68.939% when pulling ac4e741 on hanb/shutdown-warning into 834ae4e on master.

@hanbyul-here
Copy link
Contributor Author

wow @coveralls calm down.

@louh
Copy link
Contributor

louh commented Jan 6, 2018

@hanbyul-here Looks great. I made this copy-edit change to the warning:

      console.warn('Mapzen is shutting down its services including Search. Read more at https://mapzen.com/blog/shutdown. To learn more about Pelias, the open-source geocoder that powers Mapzen Search, and the Pelias team’s plan for the future, please visit http://pelias.io.');

BUT -- I no longer have push access to this repository. So I can't actually do any maintainance tasks, regrettably.

I left a checklist for publishing here: https://github.com/mapzen/leaflet-geocoder/blob/master/CONTRIBUTING.md#versioning-and-publishing

Not everything is relevant (e.g. updating dependencies and packages), but things like updating the version number and version numbers in demos should be done. I would recommend bumping this to a new minor version (so v1.10.0).

@louh
Copy link
Contributor

louh commented Jan 6, 2018

I'm happy to re-take over the maintainance duties on this repository, but I'm not sure if it's worthwhile to restore my access to this or if it's better if I work on it in a fork. I think I still have access to the npm package, actually.

cc @dianashk

@hanbyul-here
Copy link
Contributor Author

🤔 How do you think about moving this repo (or forking) to nextzen github and granting you access to that repo on nextzen? I am planning to do this for lrm-mapzen.

@hanbyul-here
Copy link
Contributor Author

Also thanks for copy editing! 🤗

@coveralls
Copy link

Coverage Status

Coverage increased (+1.1%) to 68.939% when pulling a6d3be8 on hanb/shutdown-warning into 834ae4e on master.

@coveralls
Copy link

Coverage Status

Coverage increased (+1.1%) to 68.939% when pulling a6d3be8 on hanb/shutdown-warning into 834ae4e on master.

@coveralls
Copy link

Coverage Status

Coverage increased (+1.1%) to 68.939% when pulling a6d3be8 on hanb/shutdown-warning into 834ae4e on master.

@coveralls
Copy link

Coverage Status

Coverage increased (+1.1%) to 68.939% when pulling a6d3be8 on hanb/shutdown-warning into 834ae4e on master.

@coveralls
Copy link

Coverage Status

Coverage increased (+1.1%) to 68.939% when pulling a6d3be8 on hanb/shutdown-warning into 834ae4e on master.

@coveralls
Copy link

Coverage Status

Coverage increased (+1.1%) to 68.939% when pulling a6d3be8 on hanb/shutdown-warning into 834ae4e on master.

@coveralls
Copy link

Coverage Status

Coverage increased (+1.1%) to 68.939% when pulling a6d3be8 on hanb/shutdown-warning into 834ae4e on master.

@louh
Copy link
Contributor

louh commented Jan 7, 2018

@hanbyul-here Do it and let me know!

@hanbyul-here
Copy link
Contributor Author

hanbyul-here commented Jan 10, 2018

well moving this repo to nextzen (and receiving commit permission) seems to cost :( I will merge this PR first we can talk more about where to moe this repo later.

@hanbyul-here hanbyul-here merged commit 12b663b into master Jan 10, 2018
@hanbyul-here hanbyul-here deleted the hanb/shutdown-warning branch January 10, 2018 22:20
@pelias-bot
Copy link

🎉 This PR is included in version 1.10.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants