[breken-ai]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://refine.dev/docs/guides-concepts/contributing/#commit-convention

Bugs / Features

• Related issue(s) linked
• Tests for the changes have been added
• Docs have been added / updated (not needed: no API change)
• Changesets have been added https://refine.dev/docs/guides-concepts/contributing/#creating-a-changeset

What is the current behavior?

With namingConvention: "graphql-default", getList upper-cases sort orders with upperCaseValues(camelizeKeys(generateSorting(sorters))) (packages/hasura/src/dataProvider/index.ts:164). Since nested sorting (#5508), a relation sorter like category.title produces { category: { title: "asc" } }, and upperCaseValues (packages/hasura/src/utils/upperCaseValues.ts:5) calls toUpperCase on that nested object: TypeError: v.toUpperCase is not a function.

What is the new behavior?

upperCaseValues recurses into nested objects and upper-cases only string leaves, so getList sends orderBy: { category: { title: "ASC" } }. hasura-default is unchanged.

fixes #7616

Tests: new packages/hasura/test/getList/nested-sort.spec.ts (hasura-default and graphql-default), plus a nested case in test/utils/upperCaseValues.spec.ts.

• on main @ 2352eb5b: 2 failed with TypeError: v.toUpperCase is not a function
• with this PR: hasura 160/160 passed (19 files)

Notes for reviewers

4-line change plus a @refinedev/hasura patch changeset. The GraphQL client is stubbed in the test; no live Hasura server was used. This PR was prepared by an AI agent (breken-ai) and verified with the red/green test above.

[changeset-bot]

🦋 Changeset detected

Latest commit: d522dbe

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@refinedev/hasura	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR