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

[api] transition to using IDs as primary key #1

Open
ioistired opened this issue Oct 25, 2018 · 0 comments
Open

[api] transition to using IDs as primary key #1

ioistired opened this issue Oct 25, 2018 · 0 comments
Labels
enhancement New feature or request

Comments

@ioistired
Copy link
Member

Would require a new version of the api, v1, unless we used different endpoints. Reason is snowflakes are valid emote names, so we wouldn't be able to auto detect whether the parameter is an emote or snowflake.

If done, perhaps add GET /emote/by-name/{name} which does a 301 redirect to /emote/{id}.
Or just advise users to use the /search/{query} endpoint and get the first match.

@ioistired ioistired added the enhancement New feature or request label Oct 25, 2018
@ioistired ioistired changed the title Transition to using IDs as primary key [api] transition to using IDs as primary key Oct 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant