Adding custom validate tag in open api specification
I’m trying to understand how does the open api sepcification work using go language.
Omit a field from examples but not schema with swaggo/swag in go
Using swaggo/swag in go, and I wonder if there’s a way to omit some fields in the generated examples while keeping them in the schema.
Why does Swag init only generate “general API information”?
Issue Description
Swaggo fails to recursively parse Swagger comments in Go files when using the swag init command with multiple directories and the --parseDependency and --parseInternal flags. Only the comments in the main file specified with the -g flag are parsed, while the comments in other files within the specified directories are not considered.