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

Optimize nearby endpoint. #252

Merged
merged 1 commit into from
Oct 22, 2014
Merged

Optimize nearby endpoint. #252

merged 1 commit into from
Oct 22, 2014

Conversation

monfresh
Copy link
Member

The most common way the nearby endpoint would be used is to display
locations near the one currently being visited on a map. A client would
only need a few location attributes to make use of this endpoint, such
as the name, alternate name, latitude, longitude, address, and slug.

By creating a special serializer that only returns a few attributes, we
improve the performance of the nearby endpoint.

The most common way the nearby endpoint would be used is to display
locations near the one currently being visited on a map. A client would
only need a few location attributes to make use of this endpoint, such
as the name, alternate name, latitude, longitude, address, and slug.

By creating a special serializer that only returns a few attributes, we
improve the performance of the nearby endpoint.
@coveralls
Copy link

Coverage Status

Coverage increased (+0.0%) when pulling 90ba868 on update-nearby-serializer into b5cb2fd on master.

monfresh added a commit that referenced this pull request Oct 22, 2014
@monfresh monfresh merged commit 6a8da21 into master Oct 22, 2014
@monfresh monfresh deleted the update-nearby-serializer branch October 22, 2014 21:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants