Swagger definition of the sortBy meta property and the meta and links properties breaks Golang codegen

[mikerobski]

When processing the Swagger definition to generate Golang SDK using the Swagger codegen we encountered two issues:

1. The definition of the sortBy property of the PaginatedMetaDocumented class contains the following definition of the items here:

            items: {
                oneOf: [
                    {
                        type: 'string',
                    },
                    {
                        type: 'string',
                        enum: ['ASC', 'DESC'],
                    },
                ],
            },

The result of the code generation uses item type "Object", which is invalid in Golang and breaks the code.

Replacing this definition with the following works properly by creating Golang type string of strings (SortBy [][]string):

            items: {
                    type: 'string',
            },

2. The definition of the PaginatedDocumented class contains title for the meta and links properties here:

    @ApiProperty({
        title: 'Pagination Metadata',
        required: true,
    })
    override meta!: PaginatedMetaDocumented<T>

    @ApiProperty({
        title: 'Links to pages',
        required: true,
    })
    override links!: PaginatedLinksDocumented

This forces Swagger document to wrap the type in allOf construct. See the discussion here.

Removing the title from the declaration makes the Swagger definition use direct reference of the types:

    @ApiProperty({
        required: true,
    })
    override meta!: PaginatedMetaDocumented<T>

    @ApiProperty({
        required: true,
    })
    override links!: PaginatedLinksDocumented

[Helveg]

Nice analysis of the problem! I think dropping the titles there shouldn't be an issue, but the solution to type sortBy as a string feels like a loss of information. Is there a better Swagger way to express/document that it should be column or column:ASC/column:DESC?