Johan Stenberg (MSFT)

Adding descriptions for x-ms-*-request-id headers

4

...intended usage and descriptions.

Proposal: Enable retries for non-idempotent operations using client provided "logical request" tokens.

8

# Enable retries for non-idempotent operations using client provided "logical request" tokens. Not all HTTP methods are guaranteed to be idempotent. This presents challenges when requests fail/no response is received...

Autorest (modeler four?) is incorrectly assuming that omitting "type" implies "type": "object"

5

When you don't provide a "type" attribute for a model, modeler four is unhappy and tries to "fix" it by assuming that it is an "object". However, this is (to...

...and call python directly to prep documents... ## Purpose Remove dependency on powershell on posix systems + install doc preparation scripts into a virtual environment. ## Does this introduce a...

Replace kernel builder with constructor

2

### Motivation and Context Attempt to make the code slightly more pythonic (work in progress). ### Description The builder pattern (including the chained configuration) felt a bit out of place...

Fix misleading docs in memory chain example (used the term "outputs" instead of "inputs")

```TSP model Funky { @maxLength(200) data: bytes; } ``` Result - error decorator-wrong-target Cannot apply @maxLength decorator to type it is not a string 2:3. And unhappy developer.

### Describe the bug op a(... T, two: string): void; op b is a; @@doc(b::parameters.one, "ERROR :("); @@doc(b::parameters.two, "Works :)"); ### Reproduction [playground](https://azure.github.io/typespec-azure/playground?c=b3AgYTxUIGV4dGVuZHMgVHlwZVNwZWMuUmVmbGVjdGlvbi5Nb2RlbD4oLi4uIFQsIHR3bzogc3RyaW5nKTogdm9pZDsKb3AgYiBpcyBhPHtvbmXIH30%2BOwoKQEBkb2MoYjo6cGFyYW1ldGVycy5vbmUsICJFUlJPUiA6KCIpO9UmdHdvLCAiV29ya3MgOinEJg%3D%3D&e=%40typespec%2Fopenapi3&options=%7B%7D) ### Checklist - [X] Follow our [Code...

Operations allow me to specify an interface as a return type. Well. Kind of. Should they?

8

Only the openapi emitter complains about operations returning interfaces. But otherwise it seem to compile just fine. Is that intentional? [Playground Link](https://cadlplayground.z22.web.core.windows.net/?c=aW50ZXJmYWNlIFRoaXNJc05vdEFNb2RlbCB7Cgp9CgpvcCB5b2xvKCk60CE7Cg%3D%3D)