[moetemp]

What changed?

This PR adds @nexus.varargs, @nexus.unwrap and @nexus.result-field. Together they make the Stream's publish(records) -> append-records-response into publish(*values) -> int.

/// @nexus.unwrap
record append-record { body: body-t }

resource %stream {
  /// @nexus.operation "append-records"
  /// @nexus.varargs name="values"
  /// @nexus.result-field "last-offset"
  publish: func(records: list<append-record>) -> append-records-response;
}

• @nexus.unwrap on a record with one field makes a resource method take that field's type, and wrap each value. The model and the wire keep the record.
• @nexus.varargs makes the last list parameter of a resource method variadic.
• @nexus.result-field makes a resource method return one field of the response. An unset option field of a proto with no presence gives its zero value, so an empty publish returns 0.

Python generates all three, and TypeScript and .NET get them with their client targets in follow-up PRs. Go refuses them.

Why?

The proposal has publish(*values: T) -> int, and the WIT keeps the request and the response of the proto. Each directive is general, not only for Streams.

How did you test it?

Link to a test plan if any -

• Unit Tests
• Staging
• End to End Tests

The Python stream tests check the wrapped values and the result field. A fixture checks that Go refuses them.

[moetemp]

Replaced by temporalio#372.