Repository navigation
Conversation
Rewrite the NexGen page to state each point once, add C# (NexGen v0.2.11), and describe input validation failures as a non-retryable BAD_REQUEST that the Worker returns automatically. Apply the same rewrite to the NexGen passage in the five Nexus feature guides, and add C# to the language lists in the glossary and the Java walkthrough.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
📖 Docs PR preview links
|
There was a problem hiding this comment.
🟡 Changes recommended
Related walkthrough pages still contain inconsistent validation-error handling descriptions and outdated language counts and lists that omit C#.
2 open issues
What changed in this PR
This documentation-only PR streamlines NexGen explanations, documents C# support, and aligns validation-error wording across the Nexus feature guides.
Changes:
- Consolidates the NexGen page and links to a complete contract example and SDK requirements.
- Adds C# to language lists and updates the timestamp-precision caveat.
- Describes invalid Operation input as rejected by the Worker before handler execution.
| File | Description |
|---|---|
docs/glossary.md |
Updates NexGen’s definition and supported languages. |
docs/encyclopedia/nexus/nexgen.mdx |
Consolidates explanations and updates C# and validation details. |
docs/develop/typescript/nexus/feature-guide.mdx |
Shortens contract guidance and clarifies validation errors. |
docs/develop/python/nexus/feature-guide.mdx |
Shortens contract guidance and clarifies validation errors. |
docs/develop/java/nexus/feature-guide.mdx |
Shortens contract guidance and clarifies validation errors. |
docs/develop/java/nexus/development-walkthrough/call-the-standalone-activity.mdx |
Adds C# as a cross-language caller option. |
docs/develop/go/nexus/feature-guide.mdx |
Shortens contract guidance and clarifies validation errors. |
docs/develop/dotnet/nexus/feature-guide.mdx |
Shortens contract guidance and clarifies validation errors. |
Review effort: Balanced
| - **Timeouts and escalation.** Give the approval a deadline and escalate or auto-deny when it passes. | ||
| - **Split the Workers.** Run the Nexus Service, the approval Workflow, and the notification Activity on separate Worker fleets. See [Nexus patterns](/nexus/patterns). | ||
| - **Callers in other languages.** Generate a caller from the same contract in Go, Python, or TypeScript. See [NexGen](/nexus/nexgen). | ||
| - **Callers in other languages.** Generate a caller from the same contract in C#, Go, Python, or TypeScript. See [NexGen](/nexus/nexgen). |
There was a problem hiding this comment.
Updated the walkthrough counts and language lists to include C# (five languages total) in commit a4097cb.
|
|
||
| Failures aggregate into a single error listing every violation, each naming the offending field and the constraint it broke. | ||
| A handler maps that to a `BAD_REQUEST` [Nexus handler error](/nexus/error-handling), so a malformed request tells the caller everything that was wrong in one response. | ||
| When an Operation's input fails validation, the Worker rejects it with a non-retryable `BAD_REQUEST` [Nexus handler error](/nexus/error-handling) before your Operation code runs. |
There was a problem hiding this comment.
Updated the walkthrough to match the Worker’s non-retryable BAD_REQUEST rejection before the Operation handler runs. Commit: bb45de3.
Co-authored-by: Duncanma <18338424+Duncanma@users.noreply.github.com>
Co-authored-by: Duncanma <18338424+Duncanma@users.noreply.github.com>
|
|
Summary
/nexus/nexgen): rewritten so each point is stated once. The intro leads with what NexGen generates, the "How it works" section that repeated the intro is gone, and the page links to a complete contract in the Java walkthrough.glossary.mdand the Java walkthrough'scall-the-standalone-activity.mdx.BAD_REQUEST." The page now says the Worker rejects invalid input with a non-retryableBAD_REQUESTNexus handler error before the Operation handler runs. It no longer claims the caller always receives every violation, because NexGen's spec says Go loses the details.BAD_REQUESTwording.How the BAD_REQUEST behavior was checked
NexGen's own test suites cover Go, Python, and C#. For Java and TypeScript, I sent a deliberately invalid input to the generated knowledge-base Service sample, registered on a real Worker, using a caller that skips the generated input type:
BAD_REQUEST, about 130 ms; caller receives aPayloadValidationErrorBAD_REQUEST, about 30 ms; caller receives aPayloadValidationErrorNexGen already requires Java SDK 1.39.0 or later, so the page links to NexGen's SDK requirements instead of naming versions. The handler never ran in any case.
Draft because
NexGen's C# support shipped the day before this PR. Before this is marked ready, someone on the NexGen team should confirm the C# claims and the
BAD_REQUESTwording.Checks
vale --config .vale-ci.inireports nothing on all 8 files.yarn buildwas not run.