Swag: Using channels (`chan`) causes `swag` error with `not supported`

[piwan]

Describe the bug
When using channel (chan) fields in response structure, swag init fails with message, e.g. not supported&{279 0 3 int}.

To Reproduce
Steps to reproduce the behavior:
example code:

type Response struct {
    ID      int      `json:"id"`
    control chan int `json:"-"`
}

// @Success 200 {object} Response
func GetResponse(c *gin.Context) {
}

Run swag init

Expected behavior
Why not just treating chan as an object?
Not mentioning: when this field is ignored (json:"-", as above) - I wouldn't expect swag to even look at it... (I saw also your latest swagignore, but in the code it is checked long after the getPropertyName, that fails)
If not the above, then at least, I would appreciate clear error message, currently it says: not supported&{279 0 3 int}, which seems not only missing space, but could be also more verbose in pointing more clearly what is the expression that fails.

Your swag version
swag version v1.6.5

Your go version
go version go1.14 linux/amd64

Additional context
Quick workaround, I used is to redefine (_wrap_) chan into a struct:

type Chan chan int

type Response struct {
    ID      int  `json:"id"`
    control Chan `json:"-"`
}

// @Success 200 {object} Response
func GetResponse(c *gin.Context) {
}

This actually made me think, that maybe chan should just be treated as object...

[sdghchj]

try branch refactored

[piwan]

Yes, that one works, beautiful! When do you plan to merge it?

[sdghchj]

Yes, that one works, beautiful! When do you plan to merge it?

I am not the owner of this repository, and refactor changed lots of code, merge may lead to some uncertain risk. Wait for @easonlin404 's consideration.

[cugxuan]

before the new release fixing this problem, how can I ignore this error output and do my work?

If I use the branch refactored, how can I get the new command swag?

Sorry to bother you!

[sdghchj]

before the new release fixing this problem, how can I ignore this error output and do my work?

If I use the branch refactored, how can I get the new command swag?

Sorry to bother you!

Enter dir github.com/swaggo/swag/cmd/swag, then run cmds:

git checkout refactored
go build    

[easonlin404]

m not the owner of this repository, and refactor changed lots of code, merge may lead to some uncertain risk. Wait for @easonlin404 's consideration.

@sdghchj I saw refactored branch has diverged with master. could you create a new PR?