Update to Body consistency in http request

.chronus/changes/body-consitency-2024-2-27-18-35-44-1.md

@@ -0,0 +1,23 @@
+---
+# Change versionKind to one of: internal, fix, dependencies, feature, deprecation, breaking
+changeKind: breaking
+packages:
+  - "@typespec/http"
+---
+
+Empty model after removing metadata and visibility property result in void always
+  This means the following case have changed from returning `{}` to no body
+
+  ```tsp
+  op b1(): {};
+  op b2(): {@visibility("none") prop: string};
+  op b3(): {@added(Versions.v2) prop: string};
+  ```
+
+  Workaround: Use explicit `@body`
+
+  ```tsp
+  op b1(): {@body _: {}};
+  op b2(): {@body _: {@visibility("none") prop: string}};
+  op b3(): {@body _: {@added(Versions.v2) prop: string}};
+  ```

.chronus/changes/body-consitency-2024-2-27-18-35-44-2.md

@@ -0,0 +1,18 @@
+---
+# Change versionKind to one of: internal, fix, dependencies, feature, deprecation, breaking
+changeKind: breaking
+packages:
+  - "@typespec/http"
+---
+
+Implicit status code always 200 except if response is explicitly `void`
+
+  ```tsp
+  op c1(): {@header foo: string}; // status code 200 (used to be 204)
+  ```
+
+  Solution: Add explicit `@statusCode`
+  ```tsp
+  op c1(): {@header foo: string, @statusCode _: 204};
+  op c1(): {@header foo: string, ...NoContent}; // or spread common model
+  ```

.chronus/changes/body-consitency-2024-2-27-18-35-44.md

@@ -0,0 +1,22 @@
+---
+# Change versionKind to one of: internal, fix, dependencies, feature, deprecation, breaking
+changeKind: breaking
+packages:
+  - "@typespec/http"
+---
+
+`@body` means this is the body
+
+  This change makes it that using `@body` will mean exactly this is the body and everything underneath will be included, including metadata properties. It will log a warning explaining that.
+
+  ```tsp
+  op a1(): {@body _: {@header foo: string, other: string} };
+                  ^ warning header in a body, it will not be included as a header.
+  ```
+
+  Solution use `@bodyRoot` as the goal is only to change where to resolve the body from.
+
+  ```tsp
+  op a1(): {@bodyRoot _: {@header foo: string, other: string} };
+  ```
+

.chronus/changes/body-consitency-2024-3-2-15-21-10.md

@@ -0,0 +1,9 @@
+---
+# Change versionKind to one of: internal, fix, dependencies, feature, deprecation, breaking
+changeKind: feature
+packages:
+  - "@typespec/openapi3"
+  - "@typespec/rest"
+---
+
+Add supoort for new `@bodyRoot` and `@body` distinction

.chronus/changes/body-consitency-2024-3-2-15-21-9.md

@@ -0,0 +1,18 @@
+---
+# Change versionKind to one of: internal, fix, dependencies, feature, deprecation, breaking
+changeKind: breaking
+packages:
+  - "@typespec/http"
+---
+
+Properties are not automatically omitted if everything was removed from metadata or visibility
+
+  ```tsp
+  op d1(): {headers: {@header foo: string}}; // body will be {headers: {}}
+  ```
+
+  Solution: use `@bodyIgnore`
+
+  ```tsp
+  op d1(): {@bodyIgnore headers: {@header foo: string}}; // body will be {headers: {}}
+  ```

docs/libraries/http/reference/decorators.md

@@ -10,7 +10,10 @@ toc_max_heading_level: 3
 
 ### `@body` {#@TypeSpec.Http.body}
 
-Explicitly specify that this property is to be set as the body
+Explicitly specify that this property type will be exactly the HTTP body.
+
+This means that any properties under `@body` cannot be marked as headers, query parameters, or path parameters.
+If wanting to change the resolution of the body but still mix parameters, use `@bodyRoot`.
 
 ```typespec
 @TypeSpec.Http.body
@@ -33,6 +36,69 @@ op download(): {
 };
 ```
 
+### `@bodyIgnore` {#@TypeSpec.Http.bodyIgnore}
+
+Specify that this property shouldn't be included in the HTTP body.
+This can be useful when bundling metadata together that would result in an empty property to be included in the body.
+
+```typespec
+@TypeSpec.Http.bodyIgnore
+```
+
+#### Target
+
+`ModelProperty`
+
+#### Parameters
+
+None
+
+#### Examples
+
+```typespec
+op upload(
+  name: string,
+  @bodyIgnore headers: {
+    @header id: string;
+  },
+): void;
+```
+
+### `@bodyRoot` {#@TypeSpec.Http.bodyRoot}
+
+Specify that the body resolution should be resolved from that property.
+By default the body is resolved by including all properties in the operation request/response that are not metadata.
+This allows to nest the body in a property while still allowing to use headers, query parameters, and path parameters in the same model.
+
+```typespec
+@TypeSpec.Http.bodyRoot
+```
+
+#### Target
+
+`ModelProperty`
+
+#### Parameters
+
+None
+
+#### Examples
+
+```typespec
+op upload(
+  @bodyRoot user: {
+    name: string;
+    @header id: string;
+  },
+): void;
+op download(): {
+  @bodyRoot user: {
+    name: string;
+    @header id: string;
+  };
+};
+```
+
 ### `@delete` {#@TypeSpec.Http.delete}
 
 Specify the HTTP verb for the target operation to be `DELETE`.

docs/libraries/http/reference/index.mdx

@@ -36,6 +36,8 @@ npm install --save-peer @typespec/http
 ### Decorators
 
 - [`@body`](./decorators.md#@TypeSpec.Http.body)
+- [`@bodyIgnore`](./decorators.md#@TypeSpec.Http.bodyIgnore)
+- [`@bodyRoot`](./decorators.md#@TypeSpec.Http.bodyRoot)
 - [`@delete`](./decorators.md#@TypeSpec.Http.delete)
 - [`@get`](./decorators.md#@TypeSpec.Http.get)
 - [`@head`](./decorators.md#@TypeSpec.Http.head)

packages/http/README.md

@@ -37,6 +37,8 @@ Available ruleSets:
 ### TypeSpec.Http
 
 - [`@body`](#@body)
+- [`@bodyIgnore`](#@bodyignore)
+- [`@bodyRoot`](#@bodyroot)
 - [`@delete`](#@delete)
 - [`@get`](#@get)
 - [`@head`](#@head)
@@ -55,7 +57,10 @@ Available ruleSets:
 
 #### `@body`
 
-Explicitly specify that this property is to be set as the body
+Explicitly specify that this property type will be exactly the HTTP body.
+
+This means that any properties under `@body` cannot be marked as headers, query parameters, or path parameters.
+If wanting to change the resolution of the body but still mix parameters, use `@bodyRoot`.
 
 ```typespec
 @TypeSpec.Http.body
@@ -78,6 +83,69 @@ op download(): {
 };
 ```
 
+#### `@bodyIgnore`
+
+Specify that this property shouldn't be included in the HTTP body.
+This can be useful when bundling metadata together that would result in an empty property to be included in the body.
+
+```typespec
+@TypeSpec.Http.bodyIgnore
+```
+
+##### Target
+
+`ModelProperty`
+
+##### Parameters
+
+None
+
+##### Examples
+
+```typespec
+op upload(
+  name: string,
+  @bodyIgnore headers: {
+    @header id: string;
+  },
+): void;
+```
+
+#### `@bodyRoot`
+
+Specify that the body resolution should be resolved from that property.
+By default the body is resolved by including all properties in the operation request/response that are not metadata.
+This allows to nest the body in a property while still allowing to use headers, query parameters, and path parameters in the same model.
+
+```typespec
+@TypeSpec.Http.bodyRoot
+```
+
+##### Target
+
+`ModelProperty`
+
+##### Parameters
+
+None
+
+##### Examples
+
+```typespec
+op upload(
+  @bodyRoot user: {
+    name: string;
+    @header id: string;
+  },
+): void;
+op download(): {
+  @bodyRoot user: {
+    name: string;
+    @header id: string;
+  };
+};
+```
+
 #### `@delete`
 
 Specify the HTTP verb for the target operation to be `DELETE`.

packages/http/generated-defs/TypeSpec.Http.ts

@@ -19,7 +19,10 @@ import type {
 export type StatusCodeDecorator = (context: DecoratorContext, target: ModelProperty) => void;
 
 /**
- * Explicitly specify that this property is to be set as the body
+ * Explicitly specify that this property type will be exactly the HTTP body.
+ *
+ * This means that any properties under `@body` cannot be marked as headers, query parameters, or path parameters.
+ * If wanting to change the resolution of the body but still mix parameters, use `@bodyRoot`.
  *
  * @example
  * ```typespec
@@ -84,6 +87,30 @@ export type PathDecorator = (
   paramName?: string
 ) => void;
 
+/**
+ * Specify that the body resolution should be resolved from that property.
+ * By default the body is resolved by including all properties in the operation request/response that are not metadata.
+ * This allows to nest the body in a property while still allowing to use headers, query parameters, and path parameters in the same model.
+ *
+ * @example
+ * ```typespec
+ * op upload(@bodyRoot user: {name: string, @header id: string}): void;
+ * op download(): {@bodyRoot user: {name: string, @header id: string}};
+ * ```
+ */
+export type BodyRootDecorator = (context: DecoratorContext, target: ModelProperty) => void;
+
+/**
+ * Specify that this property shouldn't be included in the HTTP body.
+ * This can be useful when bundling metadata together that would result in an empty property to be included in the body.
+ *
+ * @example
+ * ```typespec
+ * op upload(name: string, @bodyIgnore headers: {@header id: string}): void;
+ * ```
+ */
+export type BodyIgnoreDecorator = (context: DecoratorContext, target: ModelProperty) => void;
+
 /**
  * Specify the HTTP verb for the target operation to be `GET`.
  *

packages/http/generated-defs/TypeSpec.Http.ts-test.ts

@@ -1,6 +1,8 @@
 /** An error here would mean that the decorator is not exported or doesn't have the right name. */
 import {
   $body,
+  $bodyIgnore,
+  $bodyRoot,
   $delete,
   $get,
   $head,
@@ -19,6 +21,8 @@ import {
 } from "@typespec/http";
 import {
   BodyDecorator,
+  BodyIgnoreDecorator,
+  BodyRootDecorator,
   DeleteDecorator,
   GetDecorator,
   HeadDecorator,
@@ -42,6 +46,8 @@ type Decorators = {
   $header: HeaderDecorator;
   $query: QueryDecorator;
   $path: PathDecorator;
+  $bodyRoot: BodyRootDecorator;
+  $bodyIgnore: BodyIgnoreDecorator;
   $get: GetDecorator;
   $put: PutDecorator;
   $post: PostDecorator;
@@ -62,6 +68,8 @@ const _: Decorators = {
   $header,
   $query,
   $path,
+  $bodyRoot,
+  $bodyIgnore,
   $get,
   $put,
   $post,

packages/http/lib/http-decorators.tsp

@@ -83,7 +83,10 @@ extern dec query(target: ModelProperty, queryNameOrOptions?: string | QueryOptio
 extern dec path(target: ModelProperty, paramName?: valueof string);
 
 /**
- * Explicitly specify that this property is to be set as the body
+ * Explicitly specify that this property type will be exactly the HTTP body.
+ *
+ * This means that any properties under `@body` cannot be marked as headers, query parameters, or path parameters.
+ * If wanting to change the resolution of the body but still mix parameters, use `@bodyRoot`.
  *
  * @example
  *
@@ -94,6 +97,31 @@ extern dec path(target: ModelProperty, paramName?: valueof string);
  */
 extern dec body(target: ModelProperty);
 
+/**
+ * Specify that the body resolution should be resolved from that property.
+ * By default the body is resolved by including all properties in the operation request/response that are not metadata.
+ * This allows to nest the body in a property while still allowing to use headers, query parameters, and path parameters in the same model.
+ *
+ * @example
+ *
+ * ```typespec
+ * op upload(@bodyRoot user: {name: string, @header id: string}): void;
+ * op download(): {@bodyRoot user: {name: string, @header id: string}};
+ * ```
+ */
+extern dec bodyRoot(target: ModelProperty);
+/**
+ * Specify that this property shouldn't be included in the HTTP body.
+ * This can be useful when bundling metadata together that would result in an empty property to be included in the body.
+ *
+ * @example
+ *
+ * ```typespec
+ * op upload(name: string, @bodyIgnore headers: {@header id: string}): void;
+ * ```
+ */
+extern dec bodyIgnore(target: ModelProperty);
+
 /**
  * Specify the status code for this response. Property type must be a status code integer or a union of status code integer.
  *