Skip to content

Removing mention of warnings in reponse #521

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
erikmarr merged 2 commits into from
Jan 13, 2026
Merged

Removing mention of warnings in reponse #521

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
cb2b7f6
Removing mention of warnings in reponse
Jan 13, 2026
4afb300
implementing review suggestions
Jan 13, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
33 changes: 6 additions & 27 deletions src/pages/graphql/schema/live-search/queries/product-search.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -384,42 +384,21 @@ filter:[
]
```

##### Error handling for categoryPath and categoryIds
##### Error handling for categories, categoryPath, and categoryIds

When sorting by category `position` with an empty or invalid `categoryPath` or `categoryIDs`, the Search service gracefully handles the request to prevent `FAILED_PRECONDITION` errors. This scenario commonly occurs when attempting to sort by position at the root category level, where category paths are not standardized across store views.
When sorting by category `position` with an empty or invalid `categories`, `categoryPath`, or `categoryIDs`, the Search service gracefully handles the request to prevent `FAILED_PRECONDITION` errors. This scenario commonly occurs when attempting to sort by position at the root category level, where category paths are not standardized across store views.

**Behavior when an empty or invalid `categoryPath` is detected with position sorting:**
**Behavior when an empty or invalid `categories`, `categoryPath`, or `categoryIDs` is detected with position sorting:**

- Category position sort is ignored
- The system falls back to relevance-based sorting
- Products are returned successfully
- A structured GraphQL warning is included in the response

**Warning message:**

The following warning is returned in the `errors` array alongside the product data:

```json
{
"errors": [
{
"message": "Sort ignored due to empty or invalid categoryPath or categoryIds. Default sorting by relevance applied.",
"locations": [],
"extensions": {
"severity": "WARNING",
"code": "EMPTY_CATEGORY_PATH_OR_CATEGORY_IDS",
"classification": "DataFetchingException"
}
}
]
}
```

<InlineAlert variant="info" slots="text"/>

Despite the warning, the query executes successfully and returns product data in the `data` object, sorted by relevance instead of position.
Despite the empty or invalid `categories`, `categoryPath`, or `categoryIDs`, the query executes successfully and returns product data in the `data` object, sorted by relevance instead of position.

**Example query that triggers the warning:**
**Example query:**

```graphql
{
Expand Down Expand Up @@ -449,7 +428,7 @@ Despite the warning, the query executes successfully and returns product data in
}
```

In this example, the system returns products sorted by relevance with the warning message included in the response.
In this example, the system returns products sorted by relevance.

#### categories

Expand Down