[moetemp]

What changed?

This PR lets @nexus.api-omit omit a field from some targets only.

/// @nexus.api-omit targets="workflow"
/// @nexus.source targets="client" python="client_writer()"
writer: option<stream-writer>,

• @nexus.api-omit targets="workflow" drops the field from the Workflow API only. Here the client target fills it from its own source.
• A required field can be API-omitted only if it's a list<T>. A Python, TypeScript or .NET call that omits it sends it empty.
• The TypeScript model keeps a sourced field's @nexus.name, its optionality and its Long type.

In the stream sample, the Workflow read takes no last.

Why?

A Workflow read can't take last, since replay needs a fixed range, while a client read can.

How did you test it?

Link to a test plan if any -

• Unit Tests
• Staging
• End to End Tests

Python, TypeScript and .NET tests check the filled requests, and fixtures cover the refused combinations.

[moetemp]

Closing. temporalio#344 already lets @nexus.source name its targets. A source that differs per context can use one helper that checks where it runs, with targets="workflow,client". Letting a source read the definition of a create moves to a small PR on temporalio#346 later.

[moetemp]

Reopened. On top of temporalio#346 we may still need three of its rules: the private request methods fill unset sources, a source can read a create's definition, and @nexus.api-omit can name a target. It needs a rework onto temporalio#346 first.

[moetemp]

Moved to temporalio#371, on main.