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.

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

Drop /map_metadata API entry point #101

Closed
strk opened this issue Dec 16, 2013 · 6 comments
Closed

Drop /map_metadata API entry point #101

strk opened this issue Dec 16, 2013 · 6 comments
Labels

Comments

@strk
Copy link
Contributor

strk commented Dec 16, 2013

Isn't needed for a long time.
Would be nice to know since when \cc @javisantana

@strk
Copy link
Contributor Author

strk commented Dec 16, 2013

For the record, the entrypoint is unused by cartodb since version 2.0.0 ( @javisantana said )

@strk strk closed this as completed in b37b07a Dec 16, 2013
@javisantana
Copy link
Contributor

i think there is another endpoint called infowindow that we may remove too

@strk
Copy link
Contributor Author

strk commented Dec 16, 2013

The old client (from 1.0 times) is likely still using the endpoint: https://github.com/Vizzuality/cartodb-leaflet
It would be nice of us to include a tip togheter with a 404 reponse when access is made on the endpoint

@strk
Copy link
Contributor Author

strk commented Dec 16, 2013

a2e11bd

@strk strk reopened this Dec 16, 2013
@strk
Copy link
Contributor Author

strk commented Dec 16, 2013

Reverted... we need a better deprecation policy for HTTP endpoints....

strk pushed a commit that referenced this issue Dec 17, 2013
@rochoa
Copy link
Contributor

rochoa commented Feb 16, 2015

Will be removed with #257

@strk strk removed their assignment Feb 16, 2015
@rochoa rochoa mentioned this issue Mar 30, 2015
@rochoa rochoa closed this as completed Mar 30, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants