Skip to content

Misleading Error Messages #251

@gliese1337

Description

@gliese1337

I just fixed a bug in part of my code which was accidentally appending a space character at the end of resource IDs in API routes.

Figuring out that that's what was going on, however, was a little trickier than it should have been, because the error message returned by the Resource Library was not something like "that resource doesn't exist" or "that resource ID is invalid"- for some reason, it said the API key was invalid instead.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions