@typespec/http-specs 0.1.0-alpha.3-dev.6 → 0.1.0-alpha.30-dev.0

package/spec-summary.md

@@ -71,6 +71,124 @@ Expects header 'x-ms-api-key': 'valid-key'
 
 Expects header 'authorization': 'Bearer https://security.microsoft.com/.default'
 
+### Documentation_Lists_bulletPointsOp
+
+- Endpoint: `get /documentation/lists/bullet-points/op`
+
+Test simple bullet points in documentation.
+Expected behavior: Should render properly formatted bullet lists.
+
+### Documentation_Lists_numbered
+
+- Endpoint: `get /documentation/lists/numbered`
+
+Test numbered lists.
+Expected behavior: Should render numbered list properly.
+
+### Documentation_TextFormatting_boldText
+
+- Endpoint: `get /documentation/text-formatting/bold`
+
+Expected behavior: Text between \*\* should render as bold.
+
+### Documentation_TextFormatting_combinedFormatting
+
+- Endpoint: `get /documentation/text-formatting/combined`
+
+Test combined bold and italic formatting.
+Expected behavior: Should handle nested and combined formatting.
+
+### Documentation_TextFormatting_italicText
+
+- Endpoint: `get /documentation/text-formatting/italic`
+
+Test italic text formatting using _single asterisks_.
+Expected behavior: Text between \* should render as italic.
+
+### Encode_Array_Property_commaDelimited
+
+- Endpoint: `post /encode/array/property/comma-delimited`
+
+Test operation with request and response model contains a string array property with commaDelimited encode.
+Expected request body:
+
+```json
+{
+  "value": "blue,red,green"
+}
+```
+
+Expected response body:
+
+```json
+{
+  "value": "blue,red,green"
+}
+```
+
+### Encode_Array_Property_newlineDelimited
+
+- Endpoint: `post /encode/array/property/newline-delimited`
+
+Test operation with request and response model contains a string array property with newlineDelimited encode.
+Expected request body:
+
+```json
+{
+  "value": "blue\nred\ngreen"
+}
+```
+
+Expected response body:
+
+```json
+{
+  "value": "blue\nred\ngreen"
+}
+```
+
+### Encode_Array_Property_pipeDelimited
+
+- Endpoint: `post /encode/array/property/pipe-delimited`
+
+Test operation with request and response model contains a string array property with pipeDelimited encode.
+Expected request body:
+
+```json
+{
+  "value": "blue|red|green"
+}
+```
+
+Expected response body:
+
+```json
+{
+  "value": "blue|red|green"
+}
+```
+
+### Encode_Array_Property_spaceDelimited
+
+- Endpoint: `post /encode/array/property/space-delimited`
+
+Test operation with request and response model contains a string array property with spaceDelimited encode.
+Expected request body:
+
+```json
+{
+  "value": "blue red green"
+}
+```
+
+Expected response body:
+
+```json
+{
+  "value": "blue red green"
+}
+```
+
 ### Encode_Bytes_Header_base64
 
 - Endpoint: `get /encode/bytes/header/base64`
@@ -240,22 +358,21 @@ Expected body:
 - Endpoint: `post /encode/bytes/body/request/custom-content-type`
 
 When content type is a custom type(image/png here) and body is `bytes` the payload is a binary file.
-File should match packages/cadl-ranch-specs/assets/image.png
+File should match packages/http-specs/assets/image.png.
 
 ### Encode_Bytes_RequestBody_default
 
 - Endpoint: `post /encode/bytes/body/request/default`
 
-Test default encode (base64) for bytes in a json body.
-Expected body:
-"dGVzdA==" (base64 encode of test, in JSON string)
+When content type is not defined and body is `bytes` the payload is a binary stream.
+Stream should match packages/http-specs/assets/image.png file.
 
 ### Encode_Bytes_RequestBody_octetStream
 
 - Endpoint: `post /encode/bytes/body/request/octet-stream`
 
-When content type is application/octet-stream and body is `bytes` the payload is a binary file.
-File should match packages/cadl-ranch-specs/assets/image.png
+When content type is application/octet-stream and body is `bytes` the payload is a binary stream.
+Stream should match packages/http-specs/assets/image.png file.
 
 ### Encode_Bytes_ResponseBody_base64
 
@@ -278,22 +395,21 @@ Expected body:
 - Endpoint: `get /encode/bytes/body/response/custom-content-type`
 
 When content type is a custom type(image/png here) and body is `bytes` the payload is a binary file.
-File should match packages/cadl-ranch-specs/assets/image.png
+File should match packages/http-specs/assets/image.png
 
 ### Encode_Bytes_ResponseBody_default
 
 - Endpoint: `get /encode/bytes/body/response/default`
 
-Test default encode (base64) for bytes in a json body.
-Expected body:
-"dGVzdA==" (base64 encode of test, in JSON string)
+When content type is not defined and body is `bytes` the payload is a binary stream.
+Stream should match packages/http-specs/assets/image.png file.
 
 ### Encode_Bytes_ResponseBody_octetStream
 
 - Endpoint: `get /encode/bytes/body/response/octet-stream`
 
-When content type is application/octet-stream and body is `bytes` the payload is a binary file.
-File should match packages/cadl-ranch-specs/assets/image.png
+When content type is application/octet-stream and body is `bytes` the payload is a binary stream.
+Stream should match packages/http-specs/assets/image.png file.
 
 ### Encode_Datetime_Header_default
 
@@ -519,6 +635,13 @@ value=1686566864
 Test default encode for a duration header.
 Expected header `input=P40D`
 
+### Encode_Duration_Header_float64Milliseconds
+
+- Endpoint: `get /encode/duration/header/float64-milliseconds`
+
+Test float64 milliseconds encode for a duration header.
+Expected header `duration: 35625`
+
 ### Encode_Duration_Header_float64Seconds
 
 - Endpoint: `get /encode/duration/header/float64-seconds`
@@ -526,6 +649,21 @@ Expected header `input=P40D`
 Test float64 seconds encode for a duration header.
 Expected header `duration: 35.625`
 
+### Encode_Duration_Header_floatMilliseconds
+
+- Endpoint: `get /encode/duration/header/float-milliseconds`
+
+Test float milliseconds encode for a duration header.
+Expected header `duration: 35625`
+
+### Encode_Duration_Header_floatMillisecondsLargerUnit
+
+- Endpoint: `get /encode/duration/header/float-milliseconds-larger-unit`
+
+Test float milliseconds encode for a duration header where the duration is several minutes.
+Languages that support duration primitives should use the largest possible unit, e.g. TimeSpan.FromMinutes(3.5) in C#.
+Expected header `duration: 210000.0`
+
 ### Encode_Duration_Header_floatSeconds
 
 - Endpoint: `get /encode/duration/header/float-seconds`
@@ -533,6 +671,36 @@ Expected header `duration: 35.625`
 Test float seconds encode for a duration header.
 Expected header `duration: 35.625`
 
+### Encode_Duration_Header_floatSecondsLargerUnit
+
+- Endpoint: `get /encode/duration/header/float-seconds-larger-unit`
+
+Test float seconds encode for a duration header where the duration is several minutes.
+Languages that support duration primitives should use the largest possible unit, e.g. TimeSpan.FromMinutes(2.5) in C#.
+Expected header `duration: 150.0`
+
+### Encode_Duration_Header_int32Milliseconds
+
+- Endpoint: `get /encode/duration/header/int32-milliseconds`
+
+Test int32 milliseconds encode for a duration header.
+Expected header `duration: 36000`
+
+### Encode_Duration_Header_int32MillisecondsArray
+
+- Endpoint: `get /encode/duration/header/int32-milliseconds-array`
+
+Test int32 milliseconds encode for a duration array header.
+Expected header `duration: [36000,47000]`
+
+### Encode_Duration_Header_int32MillisecondsLargerUnit
+
+- Endpoint: `get /encode/duration/header/int32-milliseconds-larger-unit`
+
+Test int32 milliseconds encode for a duration header where the duration is several minutes.
+Languages that support duration primitives should use the largest possible unit, e.g. TimeSpan.FromMinutes(3) in C#.
+Expected header `duration: 180000`
+
 ### Encode_Duration_Header_int32Seconds
 
 - Endpoint: `get /encode/duration/header/int32-seconds`
@@ -540,6 +708,14 @@ Expected header `duration: 35.625`
 Test int32 seconds encode for a duration header.
 Expected header `duration: 36`
 
+### Encode_Duration_Header_int32SecondsLargerUnit
+
+- Endpoint: `get /encode/duration/header/int32-seconds-larger-unit`
+
+Test int32 seconds encode for a duration header where the duration is several minutes.
+Languages that support duration primitives should use the largest possible unit, e.g. TimeSpan.FromMinutes(2) in C#.
+Expected header `duration: 120`
+
 ### Encode_Duration_Header_iso8601
 
 - Endpoint: `get /encode/duration/header/iso8601`
@@ -575,16 +751,16 @@ Expected response body:
 }
 ```
 
-### Encode_Duration_Property_float64Seconds
+### Encode_Duration_Property_float64Milliseconds
 
-- Endpoint: `get /encode/duration/property/float64-seconds`
+- Endpoint: `get /encode/duration/property/float64-milliseconds`
 
-Test operation with request and response model contains a duration property with float64 seconds encode.
+Test operation with request and response model contains a duration property with float64 milliseconds encode.
 Expected request body:
 
 ```json
 {
-  "value": 35.625
+  "value": 35625
 }
 ```
 
@@ -592,15 +768,15 @@ Expected response body:
 
 ```json
 {
-  "value": 35.625
+  "value": 35625
 }
 ```
 
-### Encode_Duration_Property_floatSeconds
+### Encode_Duration_Property_float64Seconds
 
-- Endpoint: `get /encode/duration/property/float-seconds`
+- Endpoint: `get /encode/duration/property/float64-seconds`
 
-Test operation with request and response model contains a duration property with float seconds encode.
+Test operation with request and response model contains a duration property with float64 seconds encode.
 Expected request body:
 
 ```json
@@ -617,16 +793,16 @@ Expected response body:
 }
 ```
 
-### Encode_Duration_Property_floatSecondsArray
+### Encode_Duration_Property_floatMilliseconds
 
-- Endpoint: `get /encode/duration/property/float-seconds-array`
+- Endpoint: `get /encode/duration/property/float-milliseconds`
 
-Test operation with request and response model contains an array property which elements are duration with float seconds encode.
+Test operation with request and response model contains a duration property with float milliseconds encode.
 Expected request body:
 
 ```json
 {
-  "value": [35.625, 46.75]
+  "value": 35625
 }
 ```
 
@@ -634,20 +810,20 @@ Expected response body:
 
 ```json
 {
-  "value": [35.625, 46.75]
+  "value": 35625
 }
 ```
 
-### Encode_Duration_Property_int32Seconds
+### Encode_Duration_Property_floatMillisecondsArray
 
-- Endpoint: `get /encode/duration/property/int32-seconds`
+- Endpoint: `get /encode/duration/property/float-milliseconds-array`
 
-Test operation with request and response model contains a duration property with int32 seconds encode.
+Test operation with request and response model contains an array property which elements are duration with float milliseconds encode.
 Expected request body:
 
 ```json
 {
-  "value": 36
+  "value": [35625, 46750]
 }
 ```
 
@@ -655,20 +831,21 @@ Expected response body:
 
 ```json
 {
-  "value": 36
+  "value": [35625, 46750]
 }
 ```
 
-### Encode_Duration_Property_iso8601
+### Encode_Duration_Property_floatMillisecondsLargerUnit
 
-- Endpoint: `post /encode/duration/property/iso8601`
+- Endpoint: `get /encode/duration/property/float-milliseconds-larger-unit`
 
-Test operation with request and response model contains a duration property with iso8601 encode.
+Test operation with request and response model contains a duration property with float milliseconds encode where the duration is several minutes.
+Languages that support duration primitives should use the largest possible unit, e.g. TimeSpan.FromMinutes(3.5) in C#.
 Expected request body:
 
 ```json
 {
-  "value": "P40D"
+  "value": 210000.0
 }
 ```
 
@@ -676,62 +853,84 @@ Expected response body:
 
 ```json
 {
-  "value": "P40D"
+  "value": 210000.0
 }
 ```
 
-### Encode_Duration_Query_default
+### Encode_Duration_Property_floatSeconds
 
-- Endpoint: `get /encode/duration/query/default`
+- Endpoint: `get /encode/duration/property/float-seconds`
 
-Test default encode for a duration parameter.
-Expected query parameter `input=P40D`
+Test operation with request and response model contains a duration property with float seconds encode.
+Expected request body:
 
-### Encode_Duration_Query_float64Seconds
+```json
+{
+  "value": 35.625
+}
+```
 
-- Endpoint: `get /encode/duration/query/float64-seconds`
+Expected response body:
 
-Test float64 seconds encode for a duration parameter.
-Expected query parameter `input=35.625`
+```json
+{
+  "value": 35.625
+}
+```
 
-### Encode_Duration_Query_floatSeconds
+### Encode_Duration_Property_floatSecondsArray
 
-- Endpoint: `get /encode/duration/query/float-seconds`
+- Endpoint: `get /encode/duration/property/float-seconds-array`
 
-Test float seconds encode for a duration parameter.
-Expected query parameter `input=35.625`
+Test operation with request and response model contains an array property which elements are duration with float seconds encode.
+Expected request body:
 
-### Encode_Duration_Query_int32Seconds
+```json
+{
+  "value": [35.625, 46.75]
+}
+```
 
-- Endpoint: `get /encode/duration/query/int32-seconds`
+Expected response body:
 
-Test int32 seconds encode for a duration parameter.
-Expected query parameter `input=36`
+```json
+{
+  "value": [35.625, 46.75]
+}
+```
 
-### Encode_Duration_Query_int32SecondsArray
+### Encode_Duration_Property_floatSecondsLargerUnit
 
-- Endpoint: `get /encode/duration/query/int32-seconds-array`
+- Endpoint: `get /encode/duration/property/float-seconds-larger-unit`
 
-Test int32 seconds encode for a duration array parameter.
-Expected query parameter `input=36,47`
+Test operation with request and response model contains a duration property with float seconds encode where the duration is several minutes.
+Languages that support duration primitives should use the largest possible unit, e.g. TimeSpan.FromMinutes(2.5) in C#.
+Expected request body:
 
-### Encode_Duration_Query_iso8601
+```json
+{
+  "value": 150.0
+}
+```
 
-- Endpoint: `get /encode/duration/query/iso8601`
+Expected response body:
 
-Test iso8601 encode for a duration parameter.
-Expected query parameter `input=P40D`
+```json
+{
+  "value": 150.0
+}
+```
 
-### Encode_Numeric_Property_safeintAsString
+### Encode_Duration_Property_int32Milliseconds
 
-- Endpoint: `post /encode/numeric/property/safeint`
+- Endpoint: `get /encode/duration/property/int32-milliseconds`
 
-Test operation with request and response model contains property of safeint type with string encode.
+Test operation with request and response model contains a duration property with int32 milliseconds encode.
 Expected request body:
 
 ```json
 {
-  "value": "10000000000"
+  "value": 36000
 }
 ```
 
@@ -739,20 +938,21 @@ Expected response body:
 
 ```json
 {
-  "value": "10000000000"
+  "value": 36000
 }
 ```
 
-### Encode_Numeric_Property_uint32AsStringOptional
+### Encode_Duration_Property_int32MillisecondsLargerUnit
 
-- Endpoint: `post /encode/numeric/property/uint32`
+- Endpoint: `get /encode/duration/property/int32-milliseconds-larger-unit`
 
-Test operation with request and response model contains property of uint32 type with string encode.
+Test operation with request and response model contains a duration property with int32 milliseconds encode where the duration is several minutes.
+Languages that support duration primitives should use the largest possible unit, e.g. TimeSpan.FromMinutes(3) in C#.
 Expected request body:
 
 ```json
 {
-  "value": "1"
+  "value": 180000
 }
 ```
 
@@ -760,20 +960,20 @@ Expected response body:
 
 ```json
 {
-  "value": "1"
+  "value": 180000
 }
 ```
 
-### Encode_Numeric_Property_uint8AsString
+### Encode_Duration_Property_int32Seconds
 
-- Endpoint: `post /encode/numeric/property/uint8`
+- Endpoint: `get /encode/duration/property/int32-seconds`
 
-Test operation with request and response model contains property of uint8 type with string encode.
+Test operation with request and response model contains a duration property with int32 seconds encode.
 Expected request body:
 
 ```json
 {
-  "value": "255"
+  "value": 36
 }
 ```
 
@@ -781,52 +981,260 @@ Expected response body:
 
 ```json
 {
-  "value": "255"
+  "value": 36
 }
 ```
 
-### Parameters_Basic_ExplicitBody_simple
-
-- Endpoint: `put /parameters/basic/explicit-body/simple`
-
-Test case for simple explicit body.
-
-Should generate request body model named `User`.
-Should generate an operation like below:
-
-```
-spreadAsRequestBody(bodyParameter: BodyParameter)
-```
+### Encode_Duration_Property_int32SecondsLargerUnit
 
-Note the parameter name is guessed from the model name and it may vary by language.
+- Endpoint: `get /encode/duration/property/int32-seconds-larger-unit`
 
+Test operation with request and response model contains a duration property with int32 seconds encode where the duration is several minutes.
+Languages that support duration primitives should use the largest possible unit, e.g. TimeSpan.FromMinutes(2) in C#.
 Expected request body:
 
 ```json
-{ "name": "foo" }
+{
+  "value": 120
+}
 ```
 
-### Parameters_Basic_ImplicitBody_simple
-
-- Endpoint: `put /parameters/basic/implicit-body/simple`
+Expected response body:
 
-Test case for simple implicit body.
+```json
+{
+  "value": 120
+}
+```
 
-Should generate an operation like below:
+### Encode_Duration_Property_iso8601
 
-```
-simple(name: string)
-```
+- Endpoint: `post /encode/duration/property/iso8601`
 
+Test operation with request and response model contains a duration property with iso8601 encode.
 Expected request body:
 
 ```json
-{ "name": "foo" }
+{
+  "value": "P40D"
+}
 ```
 
-### Parameters_BodyOptionality_OptionalExplicit
+Expected response body:
 
-- Endpoints:
+```json
+{
+  "value": "P40D"
+}
+```
+
+### Encode_Duration_Query_default
+
+- Endpoint: `get /encode/duration/query/default`
+
+Test default encode for a duration parameter.
+Expected query parameter `input=P40D`
+
+### Encode_Duration_Query_float64Milliseconds
+
+- Endpoint: `get /encode/duration/query/float64-milliseconds`
+
+Test float64 milliseconds encode for a duration parameter.
+Expected query parameter `input=35625`
+
+### Encode_Duration_Query_float64Seconds
+
+- Endpoint: `get /encode/duration/query/float64-seconds`
+
+Test float64 seconds encode for a duration parameter.
+Expected query parameter `input=35.625`
+
+### Encode_Duration_Query_floatMilliseconds
+
+- Endpoint: `get /encode/duration/query/float-milliseconds`
+
+Test float milliseconds encode for a duration parameter.
+Expected query parameter `input=35625`
+
+### Encode_Duration_Query_floatMillisecondsLargerUnit
+
+- Endpoint: `get /encode/duration/query/float-milliseconds-larger-unit`
+
+Test float milliseconds encode for a duration parameter where the duration is several minutes.
+Languages that support duration primitives should use the largest possible unit, e.g. TimeSpan.FromMinutes(3.5) in C#.
+Expected query parameter `input=210000.0`
+
+### Encode_Duration_Query_floatSeconds
+
+- Endpoint: `get /encode/duration/query/float-seconds`
+
+Test float seconds encode for a duration parameter.
+Expected query parameter `input=35.625`
+
+### Encode_Duration_Query_floatSecondsLargerUnit
+
+- Endpoint: `get /encode/duration/query/float-seconds-larger-unit`
+
+Test float seconds encode for a duration parameter where the duration is several minutes.
+Languages that support duration primitives should use the largest possible unit, e.g. TimeSpan.FromMinutes(2.5) in C#.
+Expected query parameter `input=150.0`
+
+### Encode_Duration_Query_int32Milliseconds
+
+- Endpoint: `get /encode/duration/query/int32-milliseconds`
+
+Test int32 milliseconds encode for a duration parameter.
+Expected query parameter `input=36000`
+
+### Encode_Duration_Query_int32MillisecondsArray
+
+- Endpoint: `get /encode/duration/query/int32-milliseconds-array`
+
+Test int32 milliseconds encode for a duration array parameter.
+Expected query parameter `input=36000,47000`
+
+### Encode_Duration_Query_int32MillisecondsLargerUnit
+
+- Endpoint: `get /encode/duration/query/int32-milliseconds-larger-unit`
+
+Test int32 milliseconds encode for a duration parameter where the duration is several minutes.
+Languages that support duration primitives should use the largest possible unit, e.g. TimeSpan.FromMinutes(3) in C#.
+Expected query parameter `input=180000`
+
+### Encode_Duration_Query_int32Seconds
+
+- Endpoint: `get /encode/duration/query/int32-seconds`
+
+Test int32 seconds encode for a duration parameter.
+Expected query parameter `input=36`
+
+### Encode_Duration_Query_int32SecondsArray
+
+- Endpoint: `get /encode/duration/query/int32-seconds-array`
+
+Test int32 seconds encode for a duration array parameter.
+Expected query parameter `input=36,47`
+
+### Encode_Duration_Query_int32SecondsLargerUnit
+
+- Endpoint: `get /encode/duration/query/int32-seconds-larger-unit`
+
+Test int32 seconds encode for a duration parameter where the duration is several minutes.
+Languages that support duration primitives should use the largest possible unit, e.g. TimeSpan.FromMinutes(2) in C#.
+Expected query parameter `input=120`
+
+### Encode_Duration_Query_iso8601
+
+- Endpoint: `get /encode/duration/query/iso8601`
+
+Test iso8601 encode for a duration parameter.
+Expected query parameter `input=P40D`
+
+### Encode_Numeric_Property_safeintAsString
+
+- Endpoint: `post /encode/numeric/property/safeint`
+
+Test operation with request and response model contains property of safeint type with string encode.
+Expected request body:
+
+```json
+{
+  "value": "10000000000"
+}
+```
+
+Expected response body:
+
+```json
+{
+  "value": "10000000000"
+}
+```
+
+### Encode_Numeric_Property_uint32AsStringOptional
+
+- Endpoint: `post /encode/numeric/property/uint32`
+
+Test operation with request and response model contains property of uint32 type with string encode.
+Expected request body:
+
+```json
+{
+  "value": "1"
+}
+```
+
+Expected response body:
+
+```json
+{
+  "value": "1"
+}
+```
+
+### Encode_Numeric_Property_uint8AsString
+
+- Endpoint: `post /encode/numeric/property/uint8`
+
+Test operation with request and response model contains property of uint8 type with string encode.
+Expected request body:
+
+```json
+{
+  "value": "255"
+}
+```
+
+Expected response body:
+
+```json
+{
+  "value": "255"
+}
+```
+
+### Parameters_Basic_ExplicitBody_simple
+
+- Endpoint: `put /parameters/basic/explicit-body/simple`
+
+Test case for simple explicit body.
+
+Should generate request body model named `User`.
+Should generate an operation like below:
+
+```
+spreadAsRequestBody(bodyParameter: BodyParameter)
+```
+
+Note the parameter name is guessed from the model name and it may vary by language.
+
+Expected request body:
+
+```json
+{ "name": "foo" }
+```
+
+### Parameters_Basic_ImplicitBody_simple
+
+- Endpoint: `put /parameters/basic/implicit-body/simple`
+
+Test case for simple implicit body.
+
+Should generate an operation like below:
+
+```
+simple(name: string)
+```
+
+Expected request body:
+
+```json
+{ "name": "foo" }
+```
+
+### Parameters_BodyOptionality_OptionalExplicit
+
+- Endpoints:
   - `post /parameters/body-optionality/optional-explicit/set`
   - `post /parameters/body-optionality/optional-explicit/omit`
 
@@ -838,7 +1246,10 @@ Expected request body for `set`
 { "name": "foo" }
 ```
 
+Expected Content-Type header: application/json
+
 Expected no request body for `omit`
+Expected Content-Type header: must NOT be present
 
 ### Parameters_BodyOptionality_requiredExplicit
 
@@ -894,11 +1305,48 @@ This test is testing sending a pipes collection format array query parameters
 
 This test is testing sending a ssv collection format array query parameters
 
-### Parameters_CollectionFormat_Query_tsv
+### Parameters_Path_normal
+
+- Endpoint: `get /parameters/path/normal/{name}`
+
+Test case for normal path parameter.
+
+Should generate an operation like below:
+
+```
+normal(name: string)
+```
+
+Expected request path:
+
+```
+/normal/foo
+```
+
+### Parameters_Path_optional
+
+- Endpoint: `get /parameters/path/optional{/name}`
+
+Test case for optional path parameter.
+
+Should generate an operation like below:
+
+```
+optional(name?: string)
+```
+
+Expected two request:
+First request path:
+
+```
+/optional
+```
 
-- Endpoint: `get /parameters/collection-format/query/tsv`
+Second request path:
 
-This test is testing sending a tsv collection format array query parameters
+```
+/optional/foo
+```
 
 ### Parameters_Spread_Alias_spreadAsRequestBody
 
@@ -1165,7 +1613,7 @@ Expected input body:
     }
   ],
   "intValue": 1,
-  "floatValue": 1.1,
+  "floatValue": 1.25,
   "innerModel": {
     "name": "InnerMadge",
     "description": "innerDesc"
@@ -1193,7 +1641,7 @@ Expected response body:
     }
   ],
   "intValue": 1,
-  "floatValue": 1.1,
+  "floatValue": 1.25,
   "innerModel": {
     "name": "InnerMadge",
     "description": "innerDesc"
@@ -1309,9 +1757,9 @@ Expected request body is a string '{cat}'.
 Expect request (
 
 - according to https://datatracker.ietf.org/doc/html/rfc7578#section-4.4, content-type of file part shall be labeled with
-  appropriate media type, cadl-ranch will check it; content-type of other parts is optional, cadl-ranch will ignore it.
+  appropriate media type, server will check it; content-type of other parts is optional, server will ignore it.
 - according to https://datatracker.ietf.org/doc/html/rfc7578#section-4.2, filename of file part SHOULD be supplied.
-  If there are duplicated filename in same filedName, cadl-ranch can't parse them all.
+  If there are duplicated filename in same filedName, server can't parse them all.
   ):
 
 ```
@@ -1334,9 +1782,9 @@ Content-Type: application/octet-stream;
 Expect request (
 
 - according to https://datatracker.ietf.org/doc/html/rfc7578#section-4.4, content-type of file part shall be labeled with
-  appropriate media type, cadl-ranch will check it; content-type of other parts is optional, cadl-ranch will ignore it.
+  appropriate media type, server will check it; content-type of other parts is optional, server will ignore it.
 - according to https://datatracker.ietf.org/doc/html/rfc7578#section-4.2, filename of file part SHOULD be supplied.
-  If there are duplicated filename in same fieldName, cadl-ranch can't parse them all.
+  If there are duplicated filename in same fieldName, server can't parse them all.
   ):
 
 ```
@@ -1364,9 +1812,9 @@ Content-Type: application/octet-stream;
 Expect request (
 
 - according to https://datatracker.ietf.org/doc/html/rfc7578#section-4.4, content-type of file part shall be labeled with
-  appropriate media type, cadl-ranch will check it; content-type of other parts is optional, cadl-ranch will ignore it.
+  appropriate media type, server will check it; content-type of other parts is optional, server will ignore it.
 - according to https://datatracker.ietf.org/doc/html/rfc7578#section-4.2, filename of file part SHOULD be supplied.
-  If there are duplicated filename in same fieldName, cadl-ranch can't parse them all.
+  If there are duplicated filename in same fieldName, server can't parse them all.
   ):
 
 ```
@@ -1423,9 +1871,9 @@ Content-Type: image/jpg
 Expect request (
 
 - according to https://datatracker.ietf.org/doc/html/rfc7578#section-4.4, content-type of file part shall be labeled with
-  appropriate media type, cadl-ranch will check it; content-type of other parts is optional, cadl-ranch will ignore it.
+  appropriate media type, server will check it; content-type of other parts is optional, server will ignore it.
 - according to https://datatracker.ietf.org/doc/html/rfc7578#section-4.2, filename of file part SHOULD be supplied.
-  If there are duplicated filename in same fieldName, cadl-ranch can't parse them all.
+  If there are duplicated filename in same fieldName, server can't parse them all.
   ):
 
 ```
@@ -1533,7 +1981,7 @@ Content-Type: application/octet-stream
 
 - Endpoint: `post /multipart/form-data/complex-parts-with-httppart`
 
-For File part, filename will not be checked but it is necessary otherwise cadl-ranch can't parse it;
+For File part, filename will not be checked but it is necessary otherwise server can't parse it;
 content-type will be checked with value "application/octet-stream". Expect request:
 
 ```
@@ -1606,9 +2054,9 @@ Content-Type: text/plain
 Expect request (
 
 - according to https://datatracker.ietf.org/doc/html/rfc7578#section-4.4, content-type of file part shall be labeled with
-  appropriate media type, cadl-ranch will check it; content-type of other parts is optional, cadl-ranch will ignore it.
+  appropriate media type, server will check it; content-type of other parts is optional, server will ignore it.
 - according to https://datatracker.ietf.org/doc/html/rfc7578#section-4.2, filename of file part SHOULD be supplied.
-  If there are duplicated filename in same fieldName, cadl-ranch can't parse them all.
+  If there are duplicated filename in same fieldName, server can't parse them all.
   ):
 
 ```
@@ -1638,9 +2086,9 @@ Content-Type: application/octet-stream
 Please send request twice, first time with only profileImage, second time with both profileImage and picture(
 
 - according to https://datatracker.ietf.org/doc/html/rfc7578#section-4.4, content-type of file part shall be labeled with
-  appropriate media type, cadl-ranch will check it; content-type of other parts is optional, cadl-ranch will ignore it.
+  appropriate media type, server will check it; content-type of other parts is optional, server will ignore it.
 - according to https://datatracker.ietf.org/doc/html/rfc7578#section-4.2, filename of file part SHOULD be supplied.
-  If there are duplicated filename in same fieldName, cadl-ranch can't parse them all.
+  If there are duplicated filename in same fieldName, server can't parse them all.
   ):
 
 ```
@@ -1661,6 +2109,343 @@ Content-Type: application/octet-stream
 --abcde12345--
 ```
 
+### Payload_Pageable_PageSize_listWithoutContinuation
+
+- Endpoint: `get /payload/pageable/pagesize/without-continuation`
+
+Test case for simple pagination without nextlink or continuationToken.
+
+Single request:
+Expected route: /payload/pageable/pagesize/without-continuation
+
+Expected response body:
+
+```json
+{
+  "pets": [
+    { "id": "1", "name": "dog" },
+    { "id": "2", "name": "cat" },
+    { "id": "3", "name": "bird" },
+    { "id": "4", "name": "fish" }
+  ]
+}
+```
+
+### Payload_Pageable_PageSize_listWithPageSize
+
+- Endpoint: `get /payload/pageable/pagesize/list`
+
+Test case for pagination with a regular @pageSize parameter.
+
+Two requests need to be tested:
+
+1. Request with pageSize=2:
+   Expected route: /payload/pageable/pagesize/list?pageSize=2
+
+Expected response body:
+
+```json
+{
+  "pets": [
+    { "id": "1", "name": "dog" },
+    { "id": "2", "name": "cat" }
+  ]
+}
+```
+
+2. Request with pageSize=4:
+   Expected route: /payload/pageable/pagesize/list?pageSize=4
+
+Expected response body:
+
+```json
+{
+  "pets": [
+    { "id": "1", "name": "dog" },
+    { "id": "2", "name": "cat" },
+    { "id": "3", "name": "bird" },
+    { "id": "4", "name": "fish" }
+  ]
+}
+```
+
+### Payload_Pageable_ServerDrivenPagination_ContinuationToken_requestHeaderNestedResponseBody
+
+- Endpoint: `get /payload/pageable/server-driven-pagination/continuationtoken/request-header-nested-response-body`
+
+Test case for using continuation token as pagination with nested response structure. Continuation token is passed in the request header and nested within response body.
+
+Two requests need to be tested.
+
+1. Initial request:
+   Expected route: /payload/pageable/server-driven-pagination/continuationtoken/request-header-nested-response-body?bar=bar
+
+Expected request header:
+foo=foo
+
+Expected response body:
+
+```json
+{
+  "nestedItems": {
+    "pets": [
+      { "id": "1", "name": "dog" },
+      { "id": "2", "name": "cat" }
+    ]
+  },
+  "next": {
+    "nextToken": "page2"
+  }
+}
+```
+
+2. Next page request:
+   Expected route: /payload/pageable/server-driven-pagination/continuationtoken/request-header-nested-response-body?bar=bar
+
+Expected request header:
+token=page2
+foo=foo
+
+Expected response body:
+
+```json
+{
+  "nestedItems": {
+    "pets": [
+      { "id": "3", "name": "bird" },
+      { "id": "4", "name": "fish" }
+    ]
+  }
+}
+```
+
+### Payload_Pageable_ServerDrivenPagination_ContinuationToken_requestHeaderResponseBody
+
+- Endpoint: `get /payload/pageable/server-driven-pagination/continuationtoken/request-header-response-body`
+
+Test case for using continuation token as pagination. Continuation token is passed in the request header and response body.
+
+Two requests need to be tested.
+
+1. Initial request:
+   Expected route: /payload/pageable/server-driven-pagination/continuationtoken/request-header-response-body?bar=bar
+
+Expected request header:
+foo=foo
+
+Expected response body:
+
+```json
+{
+  "pets": [
+    { "id": "1", "name": "dog" },
+    { "id": "2", "name": "cat" }
+  ],
+  "nextToken": "page2"
+}
+```
+
+2. Next page request:
+   Expected route: /payload/pageable/server-driven-pagination/continuationtoken/request-header-response-body?bar=bar
+
+Expected request header:
+token=page2
+foo=foo
+
+Expected response body:
+
+```json
+{
+  "pets": [
+    { "id": "3", "name": "bird" },
+    { "id": "4", "name": "fish" }
+  ]
+}
+```
+
+### Payload_Pageable_ServerDrivenPagination_ContinuationToken_requestHeaderResponseHeader
+
+- Endpoint: `get /payload/pageable/server-driven-pagination/continuationtoken/request-header-response-header`
+
+Test case for using continuation token as pagination. Continuation token is passed in the request header and response header.
+
+Two requests need to be tested.
+
+1. Initial request:
+   Expected route: /payload/pageable/server-driven-pagination/continuationtoken/request-header-response-header?bar=bar
+
+Expected request header:
+foo=foo
+
+Expected response body:
+
+```json
+{
+  "pets": [
+    { "id": "1", "name": "dog" },
+    { "id": "2", "name": "cat" }
+  ]
+}
+```
+
+Expected response header:
+next-token=page2
+
+2. Next page request:
+   Expected route: /payload/pageable/server-driven-pagination/continuationtoken/request-header-response-header?bar=bar
+
+Expected request header:
+token=page2
+foo=foo
+
+Expected response body:
+
+```json
+{
+  "pets": [
+    { "id": "3", "name": "bird" },
+    { "id": "4", "name": "fish" }
+  ]
+}
+```
+
+### Payload_Pageable_ServerDrivenPagination_ContinuationToken_requestQueryNestedResponseBody
+
+- Endpoint: `get /payload/pageable/server-driven-pagination/continuationtoken/request-query-nested-response-body`
+
+Test case for using continuation token as pagination with nested response structure. Continuation token is passed in the request query and nested within response body.
+
+Two requests need to be tested.
+
+1. Initial request:
+   Expected route: /payload/pageable/server-driven-pagination/continuationtoken/request-query-nested-response-body?bar=bar
+
+Expected request header:
+foo=foo
+
+Expected response body:
+
+```json
+{
+  "nestedItems": {
+    "pets": [
+      { "id": "1", "name": "dog" },
+      { "id": "2", "name": "cat" }
+    ]
+  },
+  "nestedNext": {
+    "nextToken": "page2"
+  }
+}
+```
+
+2. Next page request:
+   Expected route: /payload/pageable/server-driven-pagination/continuationtoken/request-query-nested-response-body?bar=bar&token=page2
+
+Expected request header:
+foo=foo
+
+Expected response body:
+
+```json
+{
+  "nestedItems": {
+    "pets": [
+      { "id": "3", "name": "bird" },
+      { "id": "4", "name": "fish" }
+    ]
+  }
+}
+```
+
+### Payload_Pageable_ServerDrivenPagination_ContinuationToken_requestQueryResponseBody
+
+- Endpoint: `get /payload/pageable/server-driven-pagination/continuationtoken/request-query-response-body`
+
+Test case for using continuation token as pagination. Continuation token is passed in the request query and response body.
+
+Two requests need to be tested.
+
+1. Initial request:
+   Expected route: /payload/pageable/server-driven-pagination/continuationtoken/request-query-response-body?bar=bar
+
+Expected request header:
+foo=foo
+
+Expected response body:
+
+```json
+{
+  "pets": [
+    { "id": "1", "name": "dog" },
+    { "id": "2", "name": "cat" }
+  ],
+  "nextToken": "page2"
+}
+```
+
+2. Next page request:
+   Expected route: /payload/pageable/server-driven-pagination/continuationtoken/request-query-response-body?bar=bar&token=page2
+
+Expected request header:
+foo=foo
+
+Expected response body:
+
+```json
+{
+  "pets": [
+    { "id": "3", "name": "bird" },
+    { "id": "4", "name": "fish" }
+  ]
+}
+```
+
+### Payload_Pageable_ServerDrivenPagination_ContinuationToken_requestQueryResponseHeader
+
+- Endpoint: `get /payload/pageable/server-driven-pagination/continuationtoken/request-query-response-header`
+
+Test case for using continuation token as pagination. Continuation token is passed in the request query and response header.
+
+Two requests need to be tested.
+
+1. Initial request:
+   Expected route: /payload/pageable/server-driven-pagination/continuationtoken/request-query-response-header?bar=bar
+
+Expected request header:
+foo=foo
+
+Expected response body:
+
+```json
+{
+  "pets": [
+    { "id": "1", "name": "dog" },
+    { "id": "2", "name": "cat" }
+  ]
+}
+```
+
+Expected response header:
+next-token=page2
+
+2. Next page request:
+   Expected route: /payload/pageable/server-driven-pagination/continuationtoken/request-query-response-header?bar=bar&token=page2
+
+Expected request header:
+foo=foo
+
+Expected response body:
+
+```json
+{
+  "pets": [
+    { "id": "3", "name": "bird" },
+    { "id": "4", "name": "fish" }
+  ]
+}
+```
+
 ### Payload_Pageable_ServerDrivenPagination_link
 
 - Endpoint: `get /payload/pageable/server-driven-pagination/link`
@@ -1679,9 +2464,7 @@ Two requests need to be tested.
     { "id": "1", "name": "dog" },
     { "id": "2", "name": "cat" }
   ],
-  "links": {
-    "next": "http://[host]:[port]/payload/pageable/server-driven-pagination/link/nextPage"
-  }
+  "next": "http://[host]:[port]/payload/pageable/server-driven-pagination/link/nextPage"
 }
 ```
 
@@ -1698,6 +2481,82 @@ Two requests need to be tested.
 }
 ```
 
+### Payload_Pageable_ServerDrivenPagination_linkString
+
+- Endpoint: `get /payload/pageable/server-driven-pagination/link-string`
+
+Test case for using link as pagination with string nextLink.
+
+Two requests need to be tested.
+
+1. Initial request:
+   Expected route: /payload/pageable/server-driven-pagination/link-string
+   Expected response body:
+
+```json
+{
+  "pets": [
+    { "id": "1", "name": "dog" },
+    { "id": "2", "name": "cat" }
+  ],
+  "next": "http://[host]:[port]/payload/pageable/server-driven-pagination/link-string/nextPage"
+}
+```
+
+2. Next page request:
+   Expected route: /payload/pageable/server-driven-pagination/link-string/nextPage
+   Expected response body:
+
+```json
+{
+  "pets": [
+    { "id": "3", "name": "bird" },
+    { "id": "4", "name": "fish" }
+  ]
+}
+```
+
+### Payload_Pageable_ServerDrivenPagination_nestedLink
+
+- Endpoint: `get /payload/pageable/server-driven-pagination/nested-link`
+
+Test case for using link as pagination with nested structure.
+
+Two requests need to be tested.
+
+1. Initial request:
+   Expected route: /payload/pageable/server-driven-pagination/nested-link
+   Expected response body:
+
+```json
+{
+  "nestedItems": {
+    "pets": [
+      { "id": "1", "name": "dog" },
+      { "id": "2", "name": "cat" }
+    ]
+  },
+  "nestedNext": {
+    "next": "http://[host]:[port]/payload/pageable/server-driven-pagination/nested-link/nextPage"
+  }
+}
+```
+
+2. Next page request:
+   Expected route: /payload/pageable/server-driven-pagination/nested-link/nextPage
+   Expected response body:
+
+```json
+{
+  "nestedItems": {
+    "pets": [
+      { "id": "3", "name": "bird" },
+      { "id": "4", "name": "fish" }
+    ]
+  }
+}
+```
+
 ### Payload_Xml_ModelWithArrayOfModelValue_get
 
 - Endpoint: `get /payload/xml/modelWithArrayOfModel`
@@ -2084,6 +2943,40 @@ Expected request body:
 </SimpleModel>
 ```
 
+### Response_StatusCodeRange_errorResponseStatusCode404
+
+- Endpoint: `get /response/status-code-range/error-response-status-code-404`
+
+Test case for range of status code in error response.
+
+Verify that the result of the API is an error/exception in client, and the error response can be de-serialized to NotFoundError model (instead of Standard4XXError model).
+
+Expected status code 404 and response body:
+
+```json
+{
+  "code": "not-found",
+  "resourceId": "resource1"
+}
+```
+
+### Response_StatusCodeRange_errorResponseStatusCodeInRange
+
+- Endpoint: `get /response/status-code-range/error-response-status-code-in-range`
+
+Test case for range of status code in error response.
+
+Verify that the result of the API is an error/exception in client, and the error response can be de-serialized to ErrorInRange model (instead of DefaultError model).
+
+Expected status code 494 and response body:
+
+```json
+{
+  "code": "request-header-too-large",
+  "message": "Request header too large"
+}
+```
+
 ### Routes_fixed
 
 - Endpoint: `get /routes/fixed`
@@ -2120,7 +3013,7 @@ Expected path: /routes/path/explicit/a
 
 Test label expansion with explode: true when passed an array value.
 Param value: ["a","b"]
-Expected path: /routes/label/explode/array.a.b
+Expected path: /routes/path/label/explode/array.a.b
 
 ### Routes_PathParameters_LabelExpansion_Explode_primitive
 
@@ -2128,7 +3021,7 @@ Expected path: /routes/label/explode/array.a.b
 
 Test label expansion with explode: true when passed a primitive value.
 Param value: "a"
-Expected path: /routes/label/explode/primitive.a
+Expected path: /routes/path/label/explode/primitive.a
 
 ### Routes_PathParameters_LabelExpansion_Explode_record
 
@@ -2136,7 +3029,7 @@ Expected path: /routes/label/explode/primitive.a
 
 Test label expansion with explode: true when passed a record value.
 Param value: {a: 1, b: 2}
-Expected path: /routes/label/explode/record.a=1.b=2
+Expected path: /routes/path/label/explode/record.a=1.b=2
 
 ### Routes_PathParameters_LabelExpansion_Standard_array
 
@@ -2144,7 +3037,7 @@ Expected path: /routes/label/explode/record.a=1.b=2
 
 Test label expansion with explode: false when passed an array value.
 Param value: ["a","b"]
-Expected path: /routes/label/standard/array.a,b
+Expected path: /routes/path/label/standard/array.a,b
 
 ### Routes_PathParameters_LabelExpansion_Standard_primitive
 
@@ -2152,7 +3045,7 @@ Expected path: /routes/label/standard/array.a,b
 
 Test label expansion with explode: false when passed a primitive value.
 Param value: "a"
-Expected path: /routes/label/standard/primitive.a
+Expected path: /routes/path/label/standard/primitive.a
 
 ### Routes_PathParameters_LabelExpansion_Standard_record
 
@@ -2160,7 +3053,7 @@ Expected path: /routes/label/standard/primitive.a
 
 Test label expansion with explode: false when passed a record value.
 Param value: {a: 1, b: 2}
-Expected path: /routes/label/standard/record.a,1,b,2
+Expected path: /routes/path/label/standard/record.a,1,b,2
 
 ### Routes_PathParameters_MatrixExpansion_Explode_array
 
@@ -2168,7 +3061,7 @@ Expected path: /routes/label/standard/record.a,1,b,2
 
 Test matrix expansion with explode: true when passed an array value.
 Param value: ["a","b"]
-Expected path: /routes/matrix/explode/array;a.b
+Expected path: /routes/path/matrix/explode/array;param=a;param=b
 
 ### Routes_PathParameters_MatrixExpansion_Explode_primitive
 
@@ -2176,7 +3069,7 @@ Expected path: /routes/matrix/explode/array;a.b
 
 Test matrix expansion with explode: true when passed a primitive value.
 Param value: "a"
-Expected path: /routes/matrix/explode/primitive;a
+Expected path: /routes/path/matrix/explode/primitive;param=a
 
 ### Routes_PathParameters_MatrixExpansion_Explode_record
 
@@ -2184,7 +3077,7 @@ Expected path: /routes/matrix/explode/primitive;a
 
 Test matrix expansion with explode: true when passed a record value.
 Param value: {a: 1, b: 2}
-Expected path: /routes/matrix/explode/record;a=1;b=2
+Expected path: /routes/path/matrix/explode/record;a=1;b=2
 
 ### Routes_PathParameters_MatrixExpansion_Standard_array
 
@@ -2192,7 +3085,7 @@ Expected path: /routes/matrix/explode/record;a=1;b=2
 
 Test matrix expansion with explode: false when passed an array value.
 Param value: ["a","b"]
-Expected path: /routes/matrix/standard/array;a,b
+Expected path: /routes/path/matrix/standard/array;param=a;param=b
 
 ### Routes_PathParameters_MatrixExpansion_Standard_primitive
 
@@ -2200,7 +3093,7 @@ Expected path: /routes/matrix/standard/array;a,b
 
 Test matrix expansion with explode: false when passed a primitive value.
 Param value: "a"
-Expected path: /routes/matrix/standard/primitive;a
+Expected path: /routes/path/matrix/standard/primitive;param=a
 
 ### Routes_PathParameters_MatrixExpansion_Standard_record
 
@@ -2208,7 +3101,7 @@ Expected path: /routes/matrix/standard/primitive;a
 
 Test matrix expansion with explode: false when passed a record value.
 Param value: {a: 1, b: 2}
-Expected path: /routes/matrix/standard/record;a,1,b,2
+Expected path: /routes/path/matrix/standard/record;a=1;b=2
 
 ### Routes_PathParameters_PathExpansion_Explode_array
 
@@ -2216,7 +3109,7 @@ Expected path: /routes/matrix/standard/record;a,1,b,2
 
 Test path expansion with explode: true when passed an array value.
 Param value: ["a","b"]
-Expected path: /routes/path/explode/array/a/b
+Expected path: /routes/path/path/explode/array/a/b
 
 ### Routes_PathParameters_PathExpansion_Explode_primitive
 
@@ -2224,7 +3117,7 @@ Expected path: /routes/path/explode/array/a/b
 
 Test path expansion with explode: true when passed a primitive value.
 Param value: "a"
-Expected path: /routes/path/explode/primitive/a
+Expected path: /routes/path/path/explode/primitive/a
 
 ### Routes_PathParameters_PathExpansion_Explode_record
 
@@ -2232,7 +3125,7 @@ Expected path: /routes/path/explode/primitive/a
 
 Test path expansion with explode: true when passed a record value.
 Param value: {a: 1, b: 2}
-Expected path: /routes/path/explode/record/a=1/b=2
+Expected path: /routes/path/path/explode/record/a=1/b=2
 
 ### Routes_PathParameters_PathExpansion_Standard_array
 
@@ -2240,7 +3133,7 @@ Expected path: /routes/path/explode/record/a=1/b=2
 
 Test path expansion with explode: false when passed an array value.
 Param value: ["a","b"]
-Expected path: /routes/path/standard/array/a,b
+Expected path: /routes/path/path/standard/array/a,b
 
 ### Routes_PathParameters_PathExpansion_Standard_primitive
 
@@ -2248,7 +3141,7 @@ Expected path: /routes/path/standard/array/a,b
 
 Test path expansion with explode: false when passed a primitive value.
 Param value: "a"
-Expected path: /routes/path/standard/primitive/a
+Expected path: /routes/path/path/standard/primitive/a
 
 ### Routes_PathParameters_PathExpansion_Standard_record
 
@@ -2256,7 +3149,7 @@ Expected path: /routes/path/standard/primitive/a
 
 Test path expansion with explode: false when passed a record value.
 Param value: {a: 1, b: 2}
-Expected path: /routes/path/standard/record/a,1,b,2
+Expected path: /routes/path/path/standard/record/a,1,b,2
 
 ### Routes_PathParameters_ReservedExpansion_annotation
 
@@ -2280,7 +3173,7 @@ Expected path: "/routes/path/reserved-expansion/template/foo/bar%20baz"
 
 Test simple expansion with explode: true when passed an array value.
 Param value: ["a","b"]
-Expected path: /routes/simple/explode/arraya.b
+Expected path: /routes/path/simple/explode/arraya.b
 
 ### Routes_PathParameters_SimpleExpansion_Explode_primitive
 
@@ -2288,7 +3181,7 @@ Expected path: /routes/simple/explode/arraya.b
 
 Test simple expansion with explode: true when passed a primitive value.
 Param value: "a"
-Expected path: /routes/simple/explode/primitivea
+Expected path: /routes/path/simple/explode/primitivea
 
 ### Routes_PathParameters_SimpleExpansion_Explode_record
 
@@ -2296,7 +3189,7 @@ Expected path: /routes/simple/explode/primitivea
 
 Test simple expansion with explode: true when passed a record value.
 Param value: {a: 1, b: 2}
-Expected path: /routes/simple/explode/recorda=1,b=2
+Expected path: /routes/path/simple/explode/recorda=1,b=2
 
 ### Routes_PathParameters_SimpleExpansion_Standard_array
 
@@ -2304,7 +3197,7 @@ Expected path: /routes/simple/explode/recorda=1,b=2
 
 Test simple expansion with explode: false when passed an array value.
 Param value: ["a","b"]
-Expected path: /routes/simple/standard/arraya,b
+Expected path: /routes/path/simple/standard/arraya,b
 
 ### Routes_PathParameters_SimpleExpansion_Standard_primitive
 
@@ -2312,7 +3205,7 @@ Expected path: /routes/simple/standard/arraya,b
 
 Test simple expansion with explode: false when passed a primitive value.
 Param value: "a"
-Expected path: /routes/simple/standard/primitivea
+Expected path: /routes/path/simple/standard/primitivea
 
 ### Routes_PathParameters_SimpleExpansion_Standard_record
 
@@ -2320,7 +3213,7 @@ Expected path: /routes/simple/standard/primitivea
 
 Test simple expansion with explode: false when passed a record value.
 Param value: {a: 1, b: 2}
-Expected path: /routes/simple/standard/recorda,1,b,2
+Expected path: /routes/path/simple/standard/recorda,1,b,2
 
 ### Routes_PathParameters_templateOnly
 
@@ -2583,6 +3476,29 @@ Expected header parameters:
 
 Check we recognize Repeatability-Request-ID and Repeatability-First-Sent.
 
+### SpecialWords_ModelProperties_dictMethods
+
+- Endpoint: `get /special-words/model-properties/dict-methods`
+
+Verify that model properties can use names that are Python dict methods. These names (keys, items, values, etc.) may conflict with Python's dict class methods.
+
+Send
+
+```json
+{
+  "keys": "ok",
+  "items": "ok",
+  "values": "ok",
+  "popitem": "ok",
+  "clear": "ok",
+  "update": "ok",
+  "setdefault": "ok",
+  "pop": "ok",
+  "get": "ok",
+  "copy": "ok"
+}
+```
+
 ### SpecialWords_ModelProperties_sameAsModel
 
 - Endpoint: `get /special-words/model-properties/same-as-model`
@@ -3327,6 +4243,18 @@ Verify that the name "with" works. Send this parameter to pass with value `ok`.
 
 Verify that the name "yield" works. Send this parameter to pass with value `ok`.
 
+### Streaming_Jsonl_Basic_receive
+
+- Endpoint: `get /streaming/jsonl/basic/receive`
+
+Basic jsonl streaming for response.
+
+### Streaming_Jsonl_Basic_send
+
+- Endpoint: `post /streaming/jsonl/basic/send`
+
+Basic jsonl streaming for request.
+
 ### Type_Array_BooleanValue_get
 
 - Endpoint: `get /type/array/boolean`
@@ -4360,77 +5288,6 @@ Expected input body:
 }
 ```
 
-### Type_Model_Templated_float32Type
-
-- Endpoint: `put /type/model/templated/float32ValuesType`
-
-Expected input body:
-
-```json
-{
-  "kind": "Float32Values",
-  "values": [0.5],
-  "value": 0.5
-}
-```
-
-Expected response body:
-
-```json
-{
-  "kind": "Float32Values",
-  "values": [0.5],
-  "value": 0.5
-}
-```
-
-### Type_Model_Templated_int32Type
-
-- Endpoint: `put /type/model/templated/int32ValuesType`
-
-Expected input body:
-
-```json
-{
-  "kind": "Int32Values",
-  "values": [1234],
-  "value": 1234
-}
-```
-
-Expected response body:
-
-```json
-{
-  "kind": "Int32Values",
-  "values": [1234],
-  "value": 1234
-}
-```
-
-### Type_Model_Templated_numericType
-
-- Endpoint: `put /type/model/templated/numericType`
-
-Expected input body:
-
-```json
-{
-  "kind": "Int32Values",
-  "values": [1234],
-  "value": 1234
-}
-```
-
-Expected response body:
-
-```json
-{
-  "values": [1234],
-  "value": 1234
-}
-```
-
 ### Type_Model_Usage_input
 
 - Endpoint: `get /type/model/usage/input`
@@ -4467,13 +5324,7 @@ Expected input body:
 - Endpoint: `get /type/model/visibility`
 
 Generate and receive output model with readonly properties.
-Expected input body:
-
-```json
-{
-  "queryProp": 123
-}
-```
+Expected no body with `?queryProp=123`.
 
 Expected response body:
 
@@ -4488,13 +5339,7 @@ Expected response body:
 - Endpoint: `head /type/model/visibility`
 
 Generate abd send put model with write/create properties.
-Expected input body:
-
-```json
-{
-  "queryProp": 123
-}
-```
+Expected no body with `?queryProp=123`.
 
 ### Type_Model_Visibility_patchModel
 
@@ -5191,42 +6036,6 @@ Expected input body:
 }
 ```
 
-### Type_Property_AdditionalProperties_SpreadRecordDiscriminatedUnion_get
-
-- Endpoint: `get /type/property/additionalProperties/spreadRecordDiscriminatedUnion`
-
-Expected response body:
-
-```json
-{
-  "name": "abc",
-  "prop1": { "kind": "kind0", "fooProp": "abc" },
-  "prop2": {
-    "kind": "kind1",
-    "start": "2021-01-01T00:00:00Z",
-    "end": "2021-01-02T00:00:00Z"
-  }
-}
-```
-
-### Type_Property_AdditionalProperties_SpreadRecordDiscriminatedUnion_put
-
-- Endpoint: `put /type/property/additionalProperties/spreadRecordDiscriminatedUnion`
-
-Expected input body:
-
-```json
-{
-  "name": "abc",
-  "prop1": { "kind": "kind0", "fooProp": "abc" },
-  "prop2": {
-    "kind": "kind1",
-    "start": "2021-01-01T00:00:00Z",
-    "end": "2021-01-02T00:00:00Z"
-  }
-}
-```
-
 ### Type_Property_AdditionalProperties_SpreadRecordNonDiscriminatedUnion_get
 
 - Endpoint: `get /type/property/additionalProperties/spreadRecordNonDiscriminatedUnion`
@@ -6989,6 +7798,178 @@ Expect to handle a unknown type value. Mock api will return 'test'
 
 Expect to send a string value. Mock api expect to receive 'test'
 
+### Type_Union_Discriminated_Envelope_Object_CustomProperties_get
+
+- Endpoint: `get /type/union/discriminated/envelope/object/custom-properties`
+
+Test discriminated union with custom property names.
+When value of query parameter "petType" is "cat" or no query parameter input, the expected response is:
+
+```json
+{
+  "petType": "cat",
+  "petData": {
+    "name": "Whiskers",
+    "meow": true
+  }
+}
+```
+
+When it is "dog", expected response is:
+
+```json
+{
+  "petType": "dog",
+  "petData": {
+    "name": "Rex",
+    "bark": false
+  }
+}
+```
+
+### Type_Union_Discriminated_Envelope_Object_CustomProperties_put
+
+- Endpoint: `put /type/union/discriminated/envelope/object/custom-properties`
+
+Test discriminated union with custom property names.
+Send the union as:
+
+```json
+{
+  "petType": "cat",
+  "petData": {
+    "name": "Whiskers",
+    "meow": true
+  }
+}
+```
+
+### Type_Union_Discriminated_Envelope_Object_Default_get
+
+- Endpoint: `get /type/union/discriminated/envelope/object/default`
+
+Test discriminated union with envelope serialization.
+When value of query parameter "kind" is "cat" or no query parameter input, the expected response is:
+
+```json
+{
+  "kind": "cat",
+  "value": {
+    "name": "Whiskers",
+    "meow": true
+  }
+}
+```
+
+When it is "dog", expected response is:
+
+```json
+{
+  "kind": "dog",
+  "value": {
+    "name": "Rex",
+    "bark": false
+  }
+}
+```
+
+### Type_Union_Discriminated_Envelope_Object_Default_put
+
+- Endpoint: `put /type/union/discriminated/envelope/object/default`
+
+Test discriminated union with envelope serialization.
+Send the union as:
+
+```json
+{
+  "kind": "cat",
+  "value": {
+    "name": "Whiskers",
+    "meow": true
+  }
+}
+```
+
+### Type_Union_Discriminated_NoEnvelope_CustomDiscriminator_get
+
+- Endpoint: `get /type/union/discriminated/no-envelope/custom-discriminator`
+
+Test discriminated union with inline discriminator and custom discriminator property name.
+When value of query parameter "type" is "cat" or no query parameter input, the expected response is:
+
+```json
+{
+  "type": "cat",
+  "name": "Whiskers",
+  "meow": true
+}
+```
+
+When it is "dog", expected response is:
+
+```json
+{
+  "type": "dog",
+  "name": "Rex",
+  "bark": false
+}
+```
+
+### Type_Union_Discriminated_NoEnvelope_CustomDiscriminator_put
+
+- Endpoint: `put /type/union/discriminated/no-envelope/custom-discriminator`
+
+Test discriminated union with inline discriminator and custom discriminator property name.
+Send the union as:
+
+```json
+{
+  "type": "cat",
+  "name": "Whiskers",
+  "meow": true
+}
+```
+
+### Type_Union_Discriminated_NoEnvelope_Default_get
+
+- Endpoint: `get /type/union/discriminated/no-envelope/default`
+
+Test discriminated union with inline discriminator.
+When value of query parameter "kind" is "cat" or no query parameter input, the expected response is:
+
+```json
+{
+  "kind": "cat",
+  "name": "Whiskers",
+  "meow": true
+}
+```
+
+When it is "dog", expected response is:
+
+```json
+{
+  "kind": "dog",
+  "name": "Rex",
+  "bark": false
+}
+```
+
+### Type_Union_Discriminated_NoEnvelope_Default_put
+
+- Endpoint: `put /type/union/discriminated/no-envelope/default`
+
+Test discriminated union with inline discriminator.
+Send the union as:
+
+```json
+{
+  "kind": "cat",
+  "name": "Whiskers",
+  "meow": true
+}
+```
+
 ### Type_Union_EnumsOnly_get
 
 - Endpoint: `get /type/union/enums-only`
@@ -7436,6 +8417,49 @@ Expected request body:
 { "prop": "foo" }
 ```
 
+### Versioning_Removed_modelV3
+
+- Endpoint: `post /versioning/removed/api-version:{version}/v3`
+
+path: "/versioning/removed/api-version:v1/v3"
+Expected request body:
+
+```json
+{ "id": "123", "enumProp": "enumMemberV1" }
+```
+
+Expected response body:
+
+```json
+{ "id": "123", "enumProp": "enumMemberV1" }
+```
+
+path: "/versioning/removed/api-version:v2preview/v3"
+Expected request body:
+
+```json
+{ "id": "123" }
+```
+
+Expected response body:
+
+```json
+{ "id": "123" }
+```
+
+path: "/versioning/removed/api-version:v2/v3"
+Expected request body:
+
+```json
+{ "id": "123", "enumProp": "enumMemberV1" }
+```
+
+Expected response body:
+
+```json
+{ "id": "123", "enumProp": "enumMemberV1" }
+```
+
 ### Versioning_Removed_v2
 
 - Endpoint: `post /versioning/removed/api-version:{version}/v2`