Skip to content

Sending sparse fields sets for a non-existent resource type does not give clear error message #28

Closed
@lindyhopchris

Description

@lindyhopchris

By accident I sent sparse fields for the post resource, instead of posts. This resulted in the following error:

{
    "errors": [
        {
            "detail": "Sparse field sets post.slug, post.synopsis, post.title are not allowed.",
            "source": {
                "parameter": "fields"
            },
            "status": "400",
            "title": "Invalid Query Parameter"
        }
    ],
    "jsonapi": {
        "version": "1.0"
    }
}

The message should probably actually say that the post resource type does not exist.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions