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

Deprecate Gets in favor of MultiGets #132

Open
bryankane opened this issue Oct 28, 2016 · 0 comments
Open

Deprecate Gets in favor of MultiGets #132

bryankane opened this issue Oct 28, 2016 · 0 comments
Assignees
@bryankane

Comments

@bryankane
Copy link
Contributor

As discussed with @saeta and @josh-newman -- gets are basically just a MultiGet of one id, so it doesn't make sense to write both Gets and MultiGets. We should add support to Naptime to convert a get to a multiGet of one element, and deprecate gets going forward. Developers will then be able to only write a multiget, and get support for both gets and multiget.
@bryankane bryankane self-assigned this Oct 28, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bryankane bryankane

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bryankane