Skip to content

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

@ioistired

Description

@ioistired

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions