x-nullable not working for response primitives

Hello,

I’m working on an API with Swashbuckle and Autorest for it’s clients. Currently all the responses that are primitive types (int, bool) become nullable (int? or bool?), but they shouldn’t be like that.

I applied a filter before in order to correct the same issue on my entities with x-nullable, but for some reason is not working on the return types.

Is there any other way to achieve this?

Example code:

/api/Alert/Remove:
    delete:
      tags:
        - Alert
      operationId: AlertRemove
      consumes: []
      produces:
        - application/json
      parameters:
        - name: id
          in: query
          required: true
          type: string
          format: uuid
      responses:
        '200':
          description: Success
          schema:
            type: boolean
            x-nullable: false

Autorest generated client method

public static bool? AlertRemove(this IAlertsClient operations, System.Guid id)
            {
                return operations.AlertRemoveAsync(id).GetAwaiter().GetResult();
            }

[fearthecowboy]

It’s possible that for responses that are primitive, we didn’t support x-nullable.

I’ll have to dig into it.

[calvaradocl]

Hi, I just wanted to check if this was on Autorest’s roadmap for the next months, because I’m currently using the last version of the --v3 generator and still the primitive types are generated as nullables.