Bogdan Ungureanu
Bogdan Ungureanu
> would be really nice to get support for 1.18! I have 1 function in my code. Our solution at the moment is to remove this generic function until this...
> would be really nice to get support for 1.18! I have 1 function in my code. Our solution at the moment is to remove this generic function until this...
@eljoth Don't you think it would be more helpful to contribute instead of criticizing? This is an open-source project, and all the features come from community contributions.
We will release a new version in the next few days.
OAS is not meant to define the values of the response but the format. You have the option to define "example" values so the API consumer may make a clue...
If you look closer at the generated [yaml](https://github.com/swaggo/swag/blob/master/example/basic/docs/swagger/swagger.yaml) file from the example/basic folder on this repository you will notice we are generating reusable responses. Last time I checked swag didn't...
Oh, I see. If you find this helpful and have some spare time, you are well come to contribute, and I will be more than happy to assist you with...
Unfortunately, this is not possible because swag doesn't parse function body.
This is an open-source project, and all contributions are welcome until they try to break things. Just a question before you jump into writing code, How do intend to handle...
All private function definitions should have a naming convention for consistency. Naming models using the `packageName + functionName + modelName` pattern sounds like a plan. I am looking forward to...