Warn usage of implicitOptionality in @patch with deprecation

[timotheeguerin]

fix #7235

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@typespec/http@9884

npm i https://pkg.pr.new/@typespec/http-specs@9884

npm i https://pkg.pr.new/@typespec/openapi3@9884

npm i https://pkg.pr.new/@typespec/rest@9884

commit: 5af3a0b

[github-actions]

All changed packages have been documented.

• ✅ @typespec/http-specs
• ✅ @typespec/http
• ✅ @typespec/rest

Show changes

@typespec/http-specs - internal ✏️

Add suppressions for deprecated behavior

@typespec/rest - internal ✏️

Add suppressions for deprecated behavior

@typespec/http - deprecation ✏️

Deprecate use of @patch(#{implicitOptionality: true}).,> ,> Migrate using one of the following patterns depending on intended semantics:,> ,> 1. Preserve previous behavior with an explicit patch model (optional properties),> ,> diff lang=typespec,> model Pet {,> name: string;,> age: int32;,> },> ,> + model PetPatch {,> + name?: string;,> + age?: int32;,> + },> ,> ,> - @patch(#{implicitOptionality: true}) op updatePet(@body patch: Pet): void;,> + @patch op updatePet(@body patch: PetPatch): void;,> ,> ,> 2. Use merge-patch semantics explicitly with MergePatchUpdate<T>,> ,> typespec,> model Pet {,> name: string;,> age: int32;,> },> ,> @patch op updatePet(@body patch: MergePatchUpdate<Pet>): void;,> ,> ,> Use MergePatchCreateOrUpdate<T> when the operation supports create-or-update behavior.

[azure-sdk]

You can try these changes here

🛝 Playground	🌐 Website	🛝 VSCode Extension

[lirenhe]

@timotheeguerin, looks this PR has been there for long time, would you continue with this effort? We don't want new Patch operations to have implicitOptionality