-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
replace github.com/go-resty/resty with gopkg.in/resty.v1 #770
Conversation
@@ -16,7 +16,7 @@ required = [ | |||
[[constraint]] | |||
# Also defined in WORKSPACE | |||
revision = "f8815663de1e64d57cdd4ee9e2b2fa96977a030e" | |||
name = "github.com/go-resty/resty" | |||
name = "gopkg.in/resty.v1" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this still work? I think since our generated files use the other import we still need to include both. I'm not sure this is a complete fix. The correct way to fix this would be to correct the generated files as well. Sorry I know that means it will be harder to get done.
I don't think we can merge this as is - |
related (for reference) - go-resty/resty#178 also https://github.com/go-resty/resty/blob/master/go.mod#L1 contains |
Did you regenerate these files or just search replace? |
@johanbrandhorst - search-replaced in the branch for now opened swagger-api/swagger-codegen#8798 - please add the details as needed. It would be great if we could move to using the latest version of swagger-codegen (2.3.1) as mentioned in #254. Currently when I try to generate code with swagger-codegen 2.3.1, I'm getting invalid Go generated:
If I understand it correctly, `a_bit_of_everything.swagger.json has definitions for the lower-case fields:
which becomes in
and contradicts usage as in the following enum:
|
I think we're more likely just to drop this dependency than update the version. I reiterate though - this will only happen after #772 has been merged. |
I'm gonna close this, lets resume the discussion in #254 |
@johanbrandhorst - as discussed on Slack, did not update generated files