fix using tab (\t) as separator for custom type names #1594
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe the PR
A bug fix.
What happened
swag fmt ...
and custom type names got reformattedswag init ...
- Problem: types for custom names not found anymoreHint: the
swag fmt
reformats the comment, using a tab (\t) as a separator between@name
and the type name.Expectation
After running
swag fmt
, the parser still finds all types.Solution
I did rework the parser using some little regEx to use any kind of whitespace.
An additional test is provided as well.
Relation issue
Issue #1150 seems somewhat related, but I don't care what the
fmt
command does, rather the problem, the parser can't find custom types.Additional context
I did run
go run github.com/swaggo/swag/cmd/swag@latest fmt
yesterday, on a larger code base and afterward all custom type names could not be found anymore. The parser did complain can't finding the type.