Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
✅ Docs build passed |
📖 Docs PR preview links
|
| @@ -0,0 +1,254 @@ | |||
| --- | |||
| id: nexus-standalone-activity | |||
| title: Nexus Standalone Activity | |||
There was a problem hiding this comment.
Reading this gave me an interesting thought . Should this doc live under SAA rather than under Nexus. The PRD names this feature is Standalone Activity: Start from Nexus, which is actually a clearer name for this. If we leave here the name really should be something like Standalone Activity Started By Nexus
There was a problem hiding this comment.
I had a lot of similar thoughts about naming confusion. I'm not at all sure!
Co-authored-by: Quinn Klassen <klassenq@gmail.com>
Co-authored-by: Quinn Klassen <klassenq@gmail.com>
…g step, split out into per SDK instead of SDK tabs
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 500d2b9c14
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| 'develop/java/nexus/temporal-operation-handler', | ||
| 'develop/java/nexus/client-code-generator', | ||
| 'develop/java/nexus/activity-backed-operations', | ||
| 'develop/java/nexus/development-walkthrough/index', |
There was a problem hiding this comment.
The sidebar exposes these new Nexus guides, but the corresponding landing pages still stop after Quickstart, Feature guide, and Standalone Operations. Readers who enter through /develop/{dotnet,go,java,python,typescript}/nexus therefore miss the new handler, Activity-backed Operation, generator, and Java walkthrough content. Add the appropriate links to docs/develop/dotnet/nexus/index.mdx, docs/develop/go/nexus/index.mdx, docs/develop/java/nexus/index.mdx, docs/develop/python/nexus/index.mdx, and docs/develop/typescript/nexus/index.mdx.
AGENTS.md reference: AGENTS.md:L240-L245
Useful? React with 👍 / 👎.
| ## Dates, times, and durations | ||
|
|
||
| TypeScript's `--date-time-types` is the only place you choose how a date or time is represented. Elsewhere the generator decides: Java uses `java.time`, Python `datetime` and `timedelta`, and Go `time.Time` and `time.Duration`. Two cases hand you the wire string to work with instead of a date type — `format: time` in Java, and every date and time format under TypeScript's default `string` mode. | ||
|
|
||
| Whichever type you get, every language writes the same bytes. Dates and times use [RFC 3339](https://www.rfc-editor.org/rfc/rfc3339), which is a profile of [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601). ISO 8601 permits many optional spellings of the same instant, and RFC 3339 narrows them to one so two systems cannot read a timestamp differently. RFC 3339 specifies timestamps rather than durations, so durations follow ISO 8601. |
There was a problem hiding this comment.
This Java-specific how-to embeds cross-language schema, naming, date/time, validation, and feature-reference material; the Go, Python, and TypeScript copies do the same. Each guide has 11 top-level headings and 15 total headings, so the language-specific task is buried in a page at the stated split threshold. Move the shared generator reference material into docs/encyclopedia/nexus/nexus-client-code-generator.mdx (or a dedicated shared reference) and retain only Java-specific installation, generation, and usage steps here.
AGENTS.md reference: AGENTS.md:L249-L253
Useful? React with 👍 / 👎.
| Back an Operation with a **Workflow** when the work has more than one step, needs to wait for something, needs to receive [messages](/sending-messages), or needs durable intermediate state. | ||
| For example, an approval that blocks for a human decision is a Workflow, not an Activity. | ||
|
|
||
| Sample code: `{code not yet live}` |
There was a problem hiding this comment.
This literal placeholder is published on every Activity-backed Operations guide (docs/develop/{dotnet,go,java,python,typescript}/nexus/activity-backed-operations.mdx), leaving readers who reach the promised sample without code or a source link. Add the live sample link or runnable sample before publishing these pages, or defer the guides until that material is available.
AGENTS.md reference: AGENTS.md:L90-L93
Useful? React with 👍 / 👎.
Note for documentation reviewers - do not review or merge. I am sending this to some internal folks as we are discussing what we want to do.
Microservice Development Walkthrough is main part of this PR.
Matching sample Java code: temporalio/samples-java#793
┆Attachments: EDU-6917 Nexus V2 Documentation - don't review or merge!!