Flaky results in uniqueness of model names from different packages

[krishna-birla]

Describe the bug
Flaky results in maintaining unique model names after #736

To Reproduce

• Have two models (structs) with same name in different packages (same package name but different parent folders).

For example in a project called Awesome, a struct called Message is in two packages, namely foo (Awesome/foo) and foo (Awesome/pkg/foo).

• Built swagger files again and again, and it shows flaky results.

Expected behavior
The struct names should be: github.com_Awesome_foo.Message and github.com_Awesome_pkg_foo.Message

Actual behavior
Sometimes the struct names are github.com_Awesome_foo.Message and foo.Message.

Only one conflicted struct is handled

Other times it is github.com_Awesome_pkg_foo.Message and foo.Message.

Your swag version
e.g. 1.6.7

Your go version
e.g. 1.14.4

Desktop (please complete the following information):

• OS: macOS 10.15.5
• Browser: Safari
• Version:

Additional context
I would expect that in case of conflict, ideally all conflicted structs should take up full names.

[sdghchj]

Sorry, I have not found a better way to make it stable.

[krishna-birla]

@sdghchj Thanks for the super quick action!

Please let me test this.

[sdghchj]

@krishna-birla I known where the problem is, but have not got a proper idea to fix it.

[krishna-birla]

Okay, please keep the issue open in that case. Sooner or later this will need fixing for sure.