Skip to content

chore: decide whether query parameters with illegal member names get a 400 #263

Closed

Description

@thomasfosterau

Task

Decide whether query parameters whose names aren't legal JSON:API member names get a 400, and implement the decision.

Why

JSON:API 1.1 §Query Parameters says a server that "encounters a query parameter that does not follow the naming conventions above, or the server does not know how to process it as a query parameter from this specification, MUST return 400 Bad Request". #148 (merged in #262) rejects only reserved names: a base name that is all a-z. Parameters whose names aren't legal member names, or that name an unsupported extension, are still ignored:

#148's acceptance criteria scoped this out ("any key carrying a non-a-z character … still ignored"). This issue records it so it isn't a silent deferral.

Scope

Related

#148 / #262 (reserved names), #261 (spec families on endpoints that don't support them).

Done when

  • One documented policy for non-member-name and unsupported-extension query parameters, with tests.

Generated by Claude Code

Activity

  1. thomasfosterau commented on Oct 21, 2026

    @thomasfosterau
    OwnerAuthor

    Owner decision (2026-10-21): answer 400 for query parameters whose names are not legal member names and for extension-namespaced parameters of extensions the API doesn't support, with an allow-list (default ["_"], for jQuery's cache-buster), following #262's pattern.


    Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionFurther information is requested

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions