fix: validate negative offset and limit in graphql resolver

Merged
DH
6mo ago
+24-0

Closes #7474

What

Adds input validation in default_paginated_list_resolver to reject negative limit and offset values with a user-friendly GraphQLError before reaching the database layer.

Before

Negative values were passed through to Neo4j, resulting in a CypherSyntaxError with an unhelpful stack trace in the server logs.

After

The resolver immediately raises a GraphQLError with a clear message (limit must be a non-negative integer / offset must be a non-negative integer).

Tests

Added unit tests in backend/tests/unit/graphql/resolvers/test_resolver.py covering both limit and offset validation.