fredbi

@AlekSi no it is not. Generate spec and Generate Models do not work the same way and don't share much.

Comes from viper: https://github.com/spf13/viper/blob/master/TROUBLESHOOTING.md#cannot-find-package Solutions: 1. (favored) use go modules (enabled by default nowadays) 2. To build in GOPATH mode (GO111MODULE=off), first vendor your dependencies. Like so: ```` git clone...

Relates to #2066

@ffalor Proxy environment variables are handled by the net/http default client and the http.Transport. See https://pkg.go.dev/net/http#ProxyFromEnvironment and https://pkg.go.dev/golang.org/x/net/http/httpproxy#pkg-overview The client runtime normally uses the http.DefaultTransport (but in the case of...

Yes good proposal. minProperties, maxProperties are more in line with jsonschema validations, though

Missing context here

@ShriprasadM could you please include some valid go source to be able to reproduce the case?

I am using linux (go1.15.3). From your screenshot above, the generate spec fails on Mac AND linux with the same error. My hunch on how this works is that to...

@ShriprasadM as I've shown above, running the generate command with the proper environment set up just worked. I failed to see any evidence of how this works differently on macOS...

@utkarsh-var The issue you are referring to relates to server generation. Spec generation works differently.