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.

Sign up for GitHub

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

Jump to bottom

nextzen.js prep #453

Open
7 of 8 tasks
hanbyul-here opened this issue Jan 27, 2018 · 0 comments
Open
7 of 8 tasks

nextzen.js prep #453

hanbyul-here opened this issue Jan 27, 2018 · 0 comments
Assignees
@hanbyul-here

Comments

@hanbyul-here
Copy link
Contributor

hanbyul-here commented Jan 27, 2018 •
edited
Loading

  • move this repo to nextzen github account
  • build the script with updated leaflet geocoder
  • build with new lrm-mapzen (geocoder and lrm both have warning messages for users directly hitting Mapzen endpoint)
  • point house styles to nextzen one
  • resolve image asset url (https://github.com/mapzen/mapzen.js/blob/master/src/js/mapzen.js#L28)
  • drop the current build CI
  • change the attribution
  • drop the unified api key check. (Delegate api key check to each component.)
@hanbyul-here hanbyul-here self-assigned this Jan 27, 2018
@hanbyul-here hanbyul-here mentioned this issue Feb 1, 2018
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hanbyul-here hanbyul-here

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@hanbyul-here