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

Require developer API key for mapzen.js #332

Closed
rfriberg opened this issue Jan 5, 2017 · 1 comment
Closed

Require developer API key for mapzen.js #332

rfriberg opened this issue Jan 5, 2017 · 1 comment

Comments

@rfriberg
Copy link
Contributor

rfriberg commented Jan 5, 2017 •
edited
Loading

Following on the discussion around issue #331, we've decided to move forward with requiring a Mapzen developer API key for any instantiation of mapzen.js. This key will be used for all services requiring a Mapzen developer key (unless a separate key is provided in the specific service's options).

For now, recourse will simply be a console warning. See #331 for potential warnings (though certainly open to suggestions on improved wording.)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rfriberg