nebius/SWE-rebench-V2-PRs huggingface dataset:
Repository: nestjs/swagger
Pull request #370 (2019-11-02 14:40:46)

[next] Fix nested schema
## PR Checklist
Please check if your PR fulfills the following requirements:

- [x] The commit message follows our guidelines: https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md
- [x] Tests for the changes have been added (for bug fixes / features)
- [ ] Docs have been added / updated (for bug fixes / features)


## PR Type
What kind of change does this PR introduce?

<!-- Please check the one that applies to this PR using "x". -->
```
[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:
```

## What is the current behavior?
<!-- Please describe the current behavior that you are modifying, or link to a relevant issue. -->
Wrong usage of `$ref` for nested schema. Current behavior: `schema.$ref`
Issue Number: #369 


## What is the new behavior?
just `$ref` instead of `schema.$ref`.

## Does this PR introduce a breaking change?
```
[ ] Yes
[x] No
```

<!-- If this PR contains a breaking change, please describe the impact and migration path for existing applications below. -->


## Other information


Patch:
diff --git a/lib/services/schema-object-factory.ts b/lib/services/schema-object-factory.ts
index a555389f..b9c0c462 100644
--- a/lib/services/schema-object-factory.ts
+++ b/lib/services/schema-object-factory.ts
@@ -206,9 +206,7 @@ export class SchemaObjectFactory {
       return {
         name: metadata.name || key,
         required: metadata.required,
-        schema: {
-          $ref
-        }
+        $ref
       };
     }
     return {


Test patch:
diff --git a/test/services/schema-object-factory.spec.ts b/test/services/schema-object-factory.spec.ts
index 6105d791..e290fd8e 100644
--- a/test/services/schema-object-factory.spec.ts
+++ b/test/services/schema-object-factory.spec.ts
@@ -53,9 +53,7 @@ describe('SchemaObjectFactory', () => {
             }
           },
           profile: {
-            schema: {
-              $ref: '#/components/schemas/CreateProfileDto'
-            }
+            $ref: '#/components/schemas/CreateProfileDto'
           },
           tags: {
             items: {
@@ -108,9 +106,7 @@ describe('SchemaObjectFactory', () => {
             type: 'string'
           },
           parent: {
-            schema: {
-              $ref: '#/components/schemas/CreateUserDto'
-            }
+            $ref: '#/components/schemas/CreateUserDto'
           }
         },
         required: ['firstname', 'lastname', 'parent']
Repository: nestjs/swagger
Pull request #375 (2019-11-04 22:31:02)

Fix @ApiOperation cannot handle lazy-evaluated-type-function
## PR Checklist
Please check if your PR fulfills the following requirements:

- [x] The commit message follows our guidelines: https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md
- [x] Tests for the changes have been added (for bug fixes / features)
- [ ] Docs have been added / updated (for bug fixes / features)

## PR Type
What kind of change does this PR introduce?

```
[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:
```

## What is the current behavior?

Issue Number: #374 

## What is the new behavior?

`@ApiOperation` can now handle lazy-evaluated-type-functions.

## Does this PR introduce a breaking change?
```
[ ] Yes
[x] No
```



Patch:
diff --git a/lib/services/schema-object-factory.ts b/lib/services/schema-object-factory.ts
index b9c0c462..a7751f15 100644
--- a/lib/services/schema-object-factory.ts
+++ b/lib/services/schema-object-factory.ts
@@ -78,6 +78,10 @@ export class SchemaObjectFactory {
     schemas: SchemaObject[],
     schemaRefsStack: string[] = []
   ) {
+    if (this.isLazyTypeFunc(type as Function)) {
+      type = (type as Function)();
+    }
+
     const { prototype } = type;
     if (!prototype) {
       return '';


Test patch:
diff --git a/e2e/src/cats/cats.controller.ts b/e2e/src/cats/cats.controller.ts
index 822a904e..feeeed03 100644
--- a/e2e/src/cats/cats.controller.ts
+++ b/e2e/src/cats/cats.controller.ts
@@ -25,7 +25,7 @@ export class CatsController {
   @ApiResponse({
     status: 201,
     description: 'The record has been successfully created.',
-    type: Cat
+    type: () => Cat
   })
   @ApiResponse({ status: 403, description: 'Forbidden.' })
   async create(@Body() createCatDto: CreateCatDto): Promise<Cat> {
Repository: nestjs/swagger
Pull request #2952 (2024-05-16 17:33:44)

fix: Retain $ref when setting name property


## PR Checklist
Please check if your PR fulfills the following requirements:

- [x] The commit message follows our guidelines: https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md
- [ ] Tests for the changes have been added (for bug fixes / features)
- [ ] Docs have been added / updated (for bug fixes / features)


## PR Type
What kind of change does this PR introduce?

<!-- Please check the one that applies to this PR using "x". -->
- [x] Bugfix
- [ ] Feature
- [ ] Code style update (formatting, local variables)
- [ ] Refactoring (no functional changes, no api changes)
- [ ] Build related changes
- [ ] CI related changes
- [ ] Other... Please describe:

## What is the current behavior?
<!-- Please describe the current behavior that you are modifying, or link to a relevant issue. -->

Issue Number: #2951 


## What is the new behavior?
Setting the `name` property no longer results in a `$ref` being wrapped in `allOf`.

## Does this PR introduce a breaking change?
- [ ] Yes
- [x] No

<!-- If this PR contains a breaking change, please describe the impact and migration path for existing applications below. -->


## Other information



Patch:
diff --git a/lib/services/schema-object-factory.ts b/lib/services/schema-object-factory.ts
index 8c72bd98..4a10643a 100644
--- a/lib/services/schema-object-factory.ts
+++ b/lib/services/schema-object-factory.ts
@@ -365,7 +365,7 @@ export class SchemaObjectFactory {
     if (metadata.isArray) {
       return this.transformToArraySchemaProperty(metadata, key, { $ref });
     }
-    const keysToRemove = ['type', 'isArray', 'required'];
+    const keysToRemove = ['type', 'isArray', 'required', 'name'];
     const validMetadataObject = omit(metadata, keysToRemove);
     const extraMetadataKeys = Object.keys(validMetadataObject);
 


Test patch:
diff --git a/test/services/fixtures/create-profile.dto.ts b/test/services/fixtures/create-profile.dto.ts
index 30ad7493..283e0275 100644
--- a/test/services/fixtures/create-profile.dto.ts
+++ b/test/services/fixtures/create-profile.dto.ts
@@ -10,7 +10,8 @@ export class CreateProfileDto {
   lastname: string;
 
   @ApiProperty({
-    type: () => CreateUserDto
+    type: () => CreateUserDto,
+    name: 'parent'
   })
   parent: CreateUserDto;
 }
Repository: nestjs/swagger
Pull request #3164 (2024-11-13 16:42:39)

fix: @ApiSchema inheritance
Ensure the correct @ApiSchema name is used when inheriting from a base class.

## PR Checklist
Please check if your PR fulfills the following requirements:

- [x] The commit message follows our guidelines: https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md
- [x] Tests for the changes have been added (for bug fixes / features)
- [ ] Docs have been added / updated (for bug fixes / features)


## PR Type
What kind of change does this PR introduce?

<!-- Please check the one that applies to this PR using "x". -->
- [x] Bugfix
- [ ] Feature
- [ ] Code style update (formatting, local variables)
- [ ] Refactoring (no functional changes, no api changes)
- [ ] Build related changes
- [ ] CI related changes
- [ ] Other... Please describe:

## What is the current behavior?

Issue Number: #3160


## What is the new behavior?

The correct schema name will be used


## Does this PR introduce a breaking change?
- [ ] Yes
- [x] No


## Other information

There's also a fix necessary for `getSchemaPath` (get-schema-ath.util.ts). However I have not found a single test for these utils, so I didn't add one but applied the exact same fix.


Patch:
diff --git a/lib/services/schema-object-factory.ts b/lib/services/schema-object-factory.ts
index a44f89e9..df138154 100644
--- a/lib/services/schema-object-factory.ts
+++ b/lib/services/schema-object-factory.ts
@@ -292,7 +292,7 @@ export class SchemaObjectFactory {
       return type.name;
     }
 
-    const schemaName = customSchema[0].name;
+    const schemaName = customSchema[customSchema.length - 1].name;
     return schemaName ?? type.name;
   }
 
diff --git a/lib/utils/get-schema-path.util.ts b/lib/utils/get-schema-path.util.ts
index f248aa64..d418aacc 100644
--- a/lib/utils/get-schema-path.util.ts
+++ b/lib/utils/get-schema-path.util.ts
@@ -21,7 +21,7 @@ function getSchemaNameByClass(target: Function): string {
     return target.name;
   }
 
-  return customSchema[0].name ?? target.name;
+  return customSchema[customSchema.length - 1].name ?? target.name;
 }
 
 export function refs(...models: Function[]) {


Test patch:
diff --git a/test/services/schema-object-factory.spec.ts b/test/services/schema-object-factory.spec.ts
index 767cc14b..d09714b9 100644
--- a/test/services/schema-object-factory.spec.ts
+++ b/test/services/schema-object-factory.spec.ts
@@ -412,6 +412,24 @@ describe('SchemaObjectFactory', () => {
       expect(Object.keys(schemas)).toContain('UpdateUserDto');
     });
 
+    it('should override the schema name of base class', () => {
+      @ApiSchema({
+        name: 'CreateUser'
+      })
+      class CreateUserDto {}
+
+      @ApiSchema({
+        name: 'UpdateUser'
+      })
+      class UpdateUserDto extends CreateUserDto {}
+
+      const schemas: Record<string, SchemasObject> = {};
+
+      schemaObjectFactory.exploreModelSchema(UpdateUserDto, schemas);
+
+      expect(Object.keys(schemas)).toContain('UpdateUser');
+    });
+
     it('should include extension properties', () => {
       @ApiExtension('x-test', 'value')
       class CreatUserDto {
Repository: nestjs/swagger
Pull request #3169 (2024-11-15 09:50:56)

fix: expose self required attribute for objects
## PR Checklist
Please check if your PR fulfills the following requirements:

- [x] The commit message follows our guidelines: https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md
- [x] Tests for the changes have been added (for bug fixes / features)
- [ ] Docs have been added / updated (for bug fixes / features)


## PR Type
What kind of change does this PR introduce?

<!-- Please check the one that applies to this PR using "x". -->
- [x] Bugfix
- [ ] Feature
- [ ] Code style update (formatting, local variables)
- [ ] Refactoring (no functional changes, no api changes)
- [ ] Build related changes
- [ ] CI related changes
- [ ] Other... Please describe:

## What is the current behavior?
<!-- Please describe the current behavior that you are modifying, or link to a relevant issue. -->

Issue Number: #3163


## What is the new behavior?


## Does this PR introduce a breaking change?
- [ ] Yes
- [x] No

<!-- If this PR contains a breaking change, please describe the impact and migration path for existing applications below. -->


## Other information



Patch:
diff --git a/lib/interfaces/schema-object-metadata.interface.ts b/lib/interfaces/schema-object-metadata.interface.ts
index 4b23efdc..bab0b959 100644
--- a/lib/interfaces/schema-object-metadata.interface.ts
+++ b/lib/interfaces/schema-object-metadata.interface.ts
@@ -1,6 +1,6 @@
 import { Type } from '@nestjs/common';
 import { EnumSchemaAttributes } from './enum-schema-attributes.interface';
-import { SchemaObject } from './open-api-spec.interface';
+import { ReferenceObject, SchemaObject } from './open-api-spec.interface';
 
 export type EnumAllowedTypes =
   | any[]
@@ -38,4 +38,12 @@ export type SchemaObjectMetadata =
       type: 'object';
       properties: Record<string, SchemaObjectMetadata>;
       required?: string[];
+      selfRequired?: boolean;
+    } & SchemaObjectCommonMetadata)
+  | ({
+      type: 'object';
+      properties?: Record<string, SchemaObjectMetadata>;
+      additionalProperties: SchemaObject | ReferenceObject | boolean;
+      required?: string[];
+      selfRequired?: boolean;
     } & SchemaObjectCommonMetadata);


Test patch:
diff --git a/e2e/api-spec.json b/e2e/api-spec.json
index 94527952..677c0b47 100644
--- a/e2e/api-spec.json
+++ b/e2e/api-spec.json
@@ -1690,6 +1690,7 @@
           "createdAt",
           "urls",
           "_options",
+          "rawDefinition",
           "enum",
           "enumArr",
           "enumWithRef",
diff --git a/e2e/src/cats/classes/cat.class.ts b/e2e/src/cats/classes/cat.class.ts
index d0b5f206..0c47fffd 100644
--- a/e2e/src/cats/classes/cat.class.ts
+++ b/e2e/src/cats/classes/cat.class.ts
@@ -57,7 +57,8 @@ export class Cat {
         example: 400
       }
     },
-    required: ['name', 'status']
+    required: ['name', 'status'],
+    selfRequired: true
   })
   rawDefinition?: Record<string, any>;
Repository: nestjs/swagger
Pull request #3232 (2025-01-10 04:41:01)

fix: missing ApiProperty enum undefined handling
## PR Checklist
Please check if your PR fulfills the following requirements:

- [X] The commit message follows our guidelines: https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md
- [X] Tests for the changes have been added (for bug fixes / features)
- [ ] Docs have been added / updated (for bug fixes / features)


## PR Type
What kind of change does this PR introduce?

<!-- Please check the one that applies to this PR using "x". -->
- [X] Bugfix
- [ ] Feature
- [ ] Code style update (formatting, local variables)
- [ ] Refactoring (no functional changes, no api changes)
- [ ] Build related changes
- [ ] CI related changes
- [ ] Other... Please describe:

## What is the current behavior?
<!-- Please describe the current behavior that you are modifying, or link to a relevant issue. -->

Issue Number: #3229 


## What is the new behavior?

`@ApiProperty({enum: undefined})` doesn't modify type 


## Does this PR introduce a breaking change?
- [ ] Yes
- [X] No

<!-- If this PR contains a breaking change, please describe the impact and migration path for existing applications below. -->


## Other information



Patch:
diff --git a/lib/decorators/api-property.decorator.ts b/lib/decorators/api-property.decorator.ts
index c701ca86..36b75b73 100644
--- a/lib/decorators/api-property.decorator.ts
+++ b/lib/decorators/api-property.decorator.ts
@@ -64,7 +64,7 @@ export function createApiPropertyDecorator(
       enum: enumValues
     };
     delete options.enum;
-  } else if ('enum' in options) {
+  } else if ('enum' in options && options.enum !== undefined) {
     const enumValues = getEnumValues(options.enum);
 
     options.enum = enumValues;


Test patch:
diff --git a/test/services/schema-object-factory.spec.ts b/test/services/schema-object-factory.spec.ts
index 7db75e12..1c4427a1 100644
--- a/test/services/schema-object-factory.spec.ts
+++ b/test/services/schema-object-factory.spec.ts
@@ -551,6 +551,28 @@ describe('SchemaObjectFactory', () => {
         required: ['arrayOfObjects']
       });
     });
+
+    it('should not use undefined enum', () => {
+      class TestDto {
+        @ApiProperty({
+          type: 'string',
+          enum: undefined
+        })
+        testString: string;
+      }
+
+      const schemas = {};
+      schemaObjectFactory.exploreModelSchema(TestDto, schemas);
+      expect(schemas[TestDto.name]).toEqual({
+        type: 'object',
+        properties: {
+          testString: {
+            type: 'string'
+          }
+        },
+        required: ['testString']
+      });
+    });
   });
 
   describe('createEnumSchemaType', () => {
Repository: nestjs/swagger
Pull request #1309 (2021-04-16 20:00:27)

feat: add format in ApiParam decorator
## PR Checklist
Please check if your PR fulfills the following requirements:

- [ ] The commit message follows our guidelines: https://github.com/nestjs/nest/blob/master/CONTRIBUTING.md
- [ ] Tests for the changes have been added (for bug fixes / features)
- [ ] Docs have been added / updated (for bug fixes / features)


## PR Type
What kind of change does this PR introduce?

<!-- Please check the one that applies to this PR using "x". -->
```
[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Other... Please describe:
```

## What is the current behavior?
<!-- Please describe the current behavior that you are modifying, or link to a relevant issue. -->

Issue Number: N/A


## What is the new behavior?


## Does this PR introduce a breaking change?
```
[ ] Yes
[ ] No
```

<!-- If this PR contains a breaking change, please describe the impact and migration path for existing applications below. -->


## Other information

kamilmysliwiec: Can you please add tests to make sure `format` property is being added in the right place?
gperdomor: @kamilmysliwiec please trigger a new build, circle ci fails due a network issue

Patch:
diff --git a/lib/decorators/api-param.decorator.ts b/lib/decorators/api-param.decorator.ts
index 694ab5d3..4e1f48b4 100644
--- a/lib/decorators/api-param.decorator.ts
+++ b/lib/decorators/api-param.decorator.ts
@@ -12,6 +12,7 @@ type ParameterOptions = Omit<ParameterObject, 'in' | 'schema'>;
 
 interface ApiParamMetadata extends ParameterOptions {
   type?: Type<unknown> | Function | [Function] | string;
+  format?: string;
   enum?: SwaggerEnumType;
   enumName?: string;
 }


Test patch:
diff --git a/test/explorer/swagger-explorer.spec.ts b/test/explorer/swagger-explorer.spec.ts
index 2fd9b6b6..c0c4b361 100644
--- a/test/explorer/swagger-explorer.spec.ts
+++ b/test/explorer/swagger-explorer.spec.ts
@@ -287,7 +287,7 @@ describe('SwaggerExplorer', () => {
       }
 
       @Get('foos/:objectId')
-      @ApiParam({ name: 'objectId', type: 'string' })
+      @ApiParam({ name: 'objectId', type: 'string', format: 'uuid' })
       @ApiQuery({ name: 'page', type: 'string' })
       @ApiOperation({ summary: 'List all Foos' })
       @ApiOkResponse({ type: [Foo] })
@@ -397,7 +397,8 @@ describe('SwaggerExplorer', () => {
           name: 'objectId',
           required: true,
           schema: {
-            type: 'string'
+            type: 'string',
+            format: 'uuid'
           }
         },
         {
Repository: stanfordnlp/dspy
Pull request #8378 (2025-06-13 22:31:48)

Improve error message on invalid lm setup
To have more explicit prompt for users on different cases of invalid LM setup. 

Specifically, we prompt users to wrap the string by dspy.LM when they use string as the LM. This is a common case, ironically I still occasionally get trapped by this. 


Patch:
diff --git a/dspy/predict/predict.py b/dspy/predict/predict.py
index 14b44f0d..50db41a9 100644
--- a/dspy/predict/predict.py
+++ b/dspy/predict/predict.py
@@ -99,7 +99,22 @@ class Predict(Module, Parameter):
 
         # Get the right LM to use.
         lm = kwargs.pop("lm", self.lm) or settings.lm
-        assert isinstance(lm, BaseLM), "No LM is loaded."
+
+        if lm is None:
+            raise ValueError(
+                "No LM is loaded. Please configure the LM using `dspy.configure(lm=dspy.LM(...))`. e.g, "
+                "`dspy.configure(lm=dspy.LM('openai/gpt-4o-mini'))`"
+            )
+
+        if isinstance(lm, str):
+            # Many users mistakenly use `dspy.configure(lm="openai/gpt-4o-mini")` instead of
+            # `dspy.configure(lm=dspy.LM("openai/gpt-4o-mini"))`, so we are providing a specific error message.
+            raise ValueError(
+                f"LM must be an instance of `dspy.BaseLM`, not a string. Instead of using a string like "
+                f"'dspy.configure(lm=\"{lm}\")', please configure the LM like 'dspy.configure(lm=dspy.LM(\"{lm}\"))'"
+            )
+        elif not isinstance(lm, BaseLM):
+            raise ValueError(f"LM must be an instance of `dspy.BaseLM`, not {type(lm)}. Received `lm={lm}`.")
 
         # If temperature is unset or <=0.15, and n > 1, set temperature to 0.7 to keep randomness.
         temperature = config.get("temperature") or lm.kwargs.get("temperature")


Test patch:
diff --git a/tests/predict/test_predict.py b/tests/predict/test_predict.py
index c1aea972..e60cd14e 100644
--- a/tests/predict/test_predict.py
+++ b/tests/predict/test_predict.py
@@ -582,6 +582,28 @@ def test_positional_arguments():
     )
 
 
+def test_error_message_on_invalid_lm_setup():
+    # No LM is loaded.
+    with pytest.raises(ValueError, match="No LM is loaded"):
+        Predict("question -> answer")(question="Why did a chicken cross the kitchen?")
+
+    # LM is a string.
+    dspy.configure(lm="openai/gpt-4o-mini")
+    with pytest.raises(ValueError) as e:
+        Predict("question -> answer")(question="Why did a chicken cross the kitchen?")
+
+    assert "LM must be an instance of `dspy.BaseLM`, not a string." in str(e.value)
+
+    def dummy_lm():
+        pass
+
+    # LM is not an instance of dspy.BaseLM.
+    dspy.configure(lm=dummy_lm)
+    with pytest.raises(ValueError) as e:
+        Predict("question -> answer")(question="Why did a chicken cross the kitchen?")
+    assert "LM must be an instance of `dspy.BaseLM`, not <class 'function'>." in str(e.value)
+
+
 @pytest.mark.parametrize("adapter_type", ["chat", "json"])
 def test_field_constraints(adapter_type):
     class SpyLM(dspy.LM):
Repository: ysugimoto/falco
Pull request #139 (2023-04-11 09:39:11)

add fastly_info.h2.fingerprint
This PR is just a workaround, we specify an undocumented fastly predefined variable.

`fastly_info.h2.fingerprint` variable seems to come from Faslty Next-Gen WAF but we could not find any documentation in Faslty site.

However, we should manage their VCL and lint them successfully so we add it as undocumented variables.




Patch:
diff --git a/__generator__/predefined.yml b/__generator__/predefined.yml
index 443bf62..702687a 100644
--- a/__generator__/predefined.yml
+++ b/__generator__/predefined.yml
@@ -10,6 +10,11 @@ fastly_info.is_cluster_shield:
   on: [MISS, FETCH]
   get: BOOL
 
+fastly_info.h2.fingerprint:
+  reference: "https://www.integralist.co.uk/posts/fastly-varnish/"
+  on: [RECV, HASH, HIT, MISS, PASS, FETCH, ERROR, DELIVER, LOG]
+  get: STRING
+
 req.backend.is_cluster:
   reference: "https://www.integralist.co.uk/posts/fastly-varnish/"
   on: [DELIVER]
diff --git a/context/predefined.go b/context/predefined.go
index ffce231..7428314 100644
--- a/context/predefined.go
+++ b/context/predefined.go
@@ -1784,6 +1784,16 @@ func predefinedVariables() Variables {
 				},
 				"h2": &Object{
 					Items: map[string]*Object{
+						"fingerprint": &Object{
+							Items: map[string]*Object{},
+							Value: &Accessor{
+								Get:       types.StringType,
+								Set:       types.NeverType,
+								Unset:     false,
+								Scopes:    RECV | HASH | HIT | MISS | PASS | FETCH | ERROR | DELIVER | LOG,
+								Reference: "https://www.integralist.co.uk/posts/fastly-varnish/",
+							},
+						},
 						"is_push": &Object{
 							Items: map[string]*Object{},
 							Value: &Accessor{


Test patch:
diff --git a/linter/linter_test.go b/linter/linter_test.go
index 18d1873..3891f64 100644
--- a/linter/linter_test.go
+++ b/linter/linter_test.go
@@ -2535,3 +2535,13 @@ sub vcl_recv {
 `
 	assertError(t, input, context.WithFastlySnippets(snippets))
 }
+
+func TestFastlyInfoH2FingerPrintCouldLint(t *testing.T) {
+	input := `
+sub vcl_recv {
+   #FASTLY RECV
+   set req.http.H2-Fingerprint = fastly_info.h2.fingerprint;
+}
+		`
+	assertNoError(t, input)
+}