Skip to content

feat(chat): add error matching and API-facing display rules#6991

Closed
pipeline1987 wants to merge 1 commit into
masterfrom
feat/chat-error-policy-utils
Closed

feat(chat): add error matching and API-facing display rules#6991
pipeline1987 wants to merge 1 commit into
masterfrom
feat/chat-error-policy-utils

Conversation

@pipeline1987
Copy link
Copy Markdown

@pipeline1987 pipeline1987 commented Apr 24, 2026

Summary

Centralize chat error classification and user-facing strings in chat utils: thread depth, recursion, max steps, max output, rate limiting, and request origin.

@codacy-production
Copy link
Copy Markdown

codacy-production Bot commented Apr 24, 2026

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 44 complexity · 2 duplication

Metric Results
Complexity 44
Duplication 2

View in Codacy

TIP This summary will be updated as you push new changes.

@pkg-pr-new
Copy link
Copy Markdown

pkg-pr-new Bot commented Apr 24, 2026

More templates

algoliasearch-helper

npm i https://pkg.pr.new/algolia/instantsearch/algoliasearch-helper@6991

instantsearch-ui-components

npm i https://pkg.pr.new/algolia/instantsearch/instantsearch-ui-components@6991

instantsearch.css

npm i https://pkg.pr.new/algolia/instantsearch/instantsearch.css@6991

instantsearch.js

npm i https://pkg.pr.new/algolia/instantsearch/instantsearch.js@6991

react-instantsearch

npm i https://pkg.pr.new/algolia/instantsearch/react-instantsearch@6991

react-instantsearch-core

npm i https://pkg.pr.new/algolia/instantsearch/react-instantsearch-core@6991

react-instantsearch-nextjs

npm i https://pkg.pr.new/algolia/instantsearch/react-instantsearch-nextjs@6991

react-instantsearch-router-nextjs

npm i https://pkg.pr.new/algolia/instantsearch/react-instantsearch-router-nextjs@6991

vue-instantsearch

npm i https://pkg.pr.new/algolia/instantsearch/vue-instantsearch@6991

commit: a04a6f9

@Haroenv Haroenv requested review from a team, FabienMotte and afrencalg and removed request for a team and Haroenv April 24, 2026 15:19
Centralize chat error classification and user-facing strings in chat utils:
thread depth, recursion, max steps, max output, rate limiting, and request
origin. Prefer unwrapped API messages over shortened local copy. Support
JSON-wrapped service payloads and optional display resolvers for extensions.

Made-with: Cursor
@pipeline1987 pipeline1987 force-pushed the feat/chat-error-policy-utils branch from 158abe9 to a04a6f9 Compare April 24, 2026 15:55
Copy link
Copy Markdown
Contributor

@Haroenv Haroenv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is a lot of code to flatten errors. Is it possible we implement this backend to ensure the error and its message get put in a less nested part of the response?

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants