@name doesn't work

[tonidy]

Describe the bug
When I upgraded swag from 1.16.3 to 1.16.4, I noticed the renaming model to display (@name) didn't work in my struct:

type CardResponse struct {
	ID   int    `json:"id"`
	Name string `json:"name"`
} // @name CardResponseV2

Expected behavior

@name should be working

Screenshots

N/A

Your swag version
swag version v1.16.4

Your go version
go version go1.23.2 darwin/arm64

Desktop (please complete the following information):

• OS: [e.g. iOS] macOS
• Browser: [e.g. chrome, safari]
• Version: [e.g. 22]

Additional context
Add any other context about the problem here.

[njacob1001]

Same issue,

type UIElement struct {
	Id          string            `json:"id"`
	UIElement    []UIElement   `json:"UIElement"`
	Title       string            `json:"title"`
} // @name UIElement

the output is

{
"internal_form_infrastructure_web_dto.UIElement": {
            "type": "object",
            "properties": {
                "UIElement": {
                    "type": "array",
                    "items": {
                        "$ref": "#/definitions/internal_form_infrastructure_web_dto.UIElement"
                    }
                },
                "id": {
                    "type": "string"
                },
                "title": {
                    "type": "string"
                }
            }
        }
}

[YlanzinhoY]

What should the correct output look like?

[tonidy]

@YlanzinhoY with this struct:

type UpdateGameConfigRequest struct {
	GameConfig model.GameConfig `json:"gameConfig" validate:"required"`
} // @name UpdateGameConfigRequest

Here is when I run my code with swag 1.6.4:

The correct output should be dto.UpdateGameConfigRequest

[temamagic]

In my case it will work when comment like // @name User, but after swag fmt // @name UpdateUser it doesn't works

[njacob1001]

This issue was introduced in the new version of swag@v2
https://github.com/swaggo/swag/releases/tag/v2.0.0-rc4

I was using the previous version v2.0.0-rc3, but after updating to v2.0.0-rc4, the issue reappeared.

[ubogdan]

Can someone take a look at it and write a PR?

[njacob1001]

I'm figuring out which commit is, I found this one #1866

from this point the command doesn't work due to invalid memory address or nil pointer dereference

I'm still working on this investigation

[njacob1001]

@ubogdan I've created this PR #1948 hope this helps to have more context about this issue, I know it is not a final solution.