When the return value defined by the @ Success tag is equal to a null value, a null pointer exception occurs

[addice1019]

Describe the bug
When the return value defined by the @ Success tag is equal to a null value, a null pointer exception occurs

To Reproduce
Steps to reproduce the behavior:

1. Response {data=nil} in the structure
   

2. Run the command swag init in cmd
   

3. Invalid memory address or nil pointer dereference discovered through debugging
   

Expected behavior
Can swaggo parse comments in the returned structure that are equal to nil, such as utils. Response {data=nil}
Expected swaggo doc definition

// deleteFile 删除文件
//
//	@Summary		删除文件
//	@Description	删除文件
//	@Tags			member
//	@Accept			json
//	@Produce		json
//	@Param			fileIds	query		string	true	"文件ID集合字符串"
//	@Success		200		{object}	utils.Response{data=nil}
//	@Failure		400		{object}	utils.ErrorResponse
//	@Router			/app/deleteFile [POST]
func deleteFile(c *gin.Context) {
}

Expected JSON return value

{
   "status": 0,
   "message": "success",
   "data": null
}

Your swag version
v1.16.1

Your go version
go1.20.5

Desktop (please complete the following information):

• OS: [windows 10 19045.3324]

[sdghchj]

May I ask why need null?

[addice1019]

The project coexists with the Springboot project and requires a unified JSON return value

[Shimizu1111]

What do you think of the solution in #1667 ?

[Shimizu1111]

@sdghchj
What do you think of the solution in #1667 ?