[moetemp]

What changed?

This PR lets @nexus.flatten-in-api apply to a field, so a call takes only some fields of that field's record.

record create-stream-request {
  /// @nexus.flatten-in-api fields="id backend"
  stream-ref: stream-ref,
}

• fields lists the fields of the record that become parameters of the call, and the call builds the record from them.
• Each required field of the record must be in fields. The field can't also have a source, a default, an api-omit or @nexus.omit.
• Python, TypeScript and .NET generate it in each target. Go refuses a field-level flatten, and Java doesn't generate proto-backed models.

Why?

The proposal has client.create_stream[T](id, *, backend=None), and the create request has the id and the backend in its stream_ref. A record-level flatten would promote every field of StreamRef in every request that has one.

How did you test it?

Link to a test plan if any -

• Unit Tests
• Staging
• End to End Tests

The Python, TypeScript and .NET tests check the ref of a Stream create. Fixtures cover the refused flattens.

[moetemp]

Moved to temporalio#368, on main. It flattens the whole record of one request field, so the fields="..." subset is gone.