-
Notifications
You must be signed in to change notification settings - Fork 48
fix: surface server error body & cap scenarios #324
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.
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
Changes from 4 commits
31edfb5
5f37f10
ea3718a
039dbd0
f2138c3
c064e62
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,3 +1,10 @@ | ||
| export const TC_DETAILS_MAX_BATCH = 10; | ||
|
|
||
| export const BULK_CREATE_MAX_BATCH = 10; | ||
|
|
||
| // Cap scenarios per document (mirrors TCG's former maxScenariosPerDocument=10). | ||
| export const MAX_SCENARIOS_PER_DOCUMENT = 10; | ||
|
SavioBS629 marked this conversation as resolved.
Outdated
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. [High] Scenarios beyond this cap are still silently discarded (unresolved) Both the The real backend constraint is 10 IDs per fetch-details request, already enforced by Suggestion: Remove Reviewer: stack:code-review |
||
|
|
||
| export const TCG_TRIGGER_URL = (baseUrl: string) => | ||
| `${baseUrl}/api/v1/integration/tcg/test-generation/suggest-test-cases`; | ||
|
|
||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[High] Drop site for the silent scenario cap
This
canAcceptScenario(..., MAX_SCENARIOS_PER_DOCUMENT)gate (and the matching one in thescenariobranch) silently skips every scenario past the 10th —fetchTestCaseDetailsis never called for it and its test cases are never created. Combined with the cappedtotalin the result string, the user gets no signal that data was dropped. See the config.ts comment for the full finding and suggested fix.Suggestion: Remove the per-document cap (chunking already handles the real per-request limit), or surface dropped scenarios in the result string.
Reviewer: stack:code-review