typespec-autorest - @Openapi.extension emit schema for Types

[chrisradek]

Depends on microsoft/typespec#6229
Fixes microsoft/typespec#6077

This PR updates @azure-tools/typespec-autorest to support emitting schemas for Types passed into the @OpenAPI.extension decorator.

[azure-sdk]

All changed packages have been documented.

• ✅ @azure-tools/typespec-autorest

Show changes

@azure-tools/typespec-autorest - breaking ✏️

Updates the @extension behavior to emit schemas for passed in Types. Values will continue to be emitted as raw data. Model and Tuple expressions that were previously treated as Values are now treated as Types.,> ,> Now the following TypeSpec:,> tsp,> @OpenAPI.extension("x-value", "custom value"),> @OpenAPI.extension("x-schema", typeof "custom value"),> model Foo {},> ,> emits the following schema:,> yaml,> Foo:,> type: object,> x-value: custom value,> x-schema:,> type: string,> enum:,> - custom value,>

[azure-sdk]

You can try these changes here

🛝 Playground	🌐 Website

[timotheeguerin]

I am a tiny bit worried about this change for the value it brings. Wondering if we might be better to just cut of the type conversion for 1.0 so at least using a type is exposed as broken with teh codefix to the user and maybe we add the feature parity in a few month.

Here I am worried that a lot of 3p customers might not pulled the last version and this would be a bigger break(quite confusing I assume as well) with no codefix