Wes McNamee
Wes McNamee
@carljthompson you are ignoring the response here: ``` _, err = jiraClient.Issue.UpdateIssue("BLAH-3001",l) ``` that `_` is the response. Read the body to get more information.
``` body, _ := ioutil.ReadAll(resp.Body) fmt.Println(string(body)) ```
@andygrunwald I think the error should be useful. ;)
I'm closing this issue, but labeling it as a reminder for v2 ideas. I think error reporting could be improved.
How would you like to see this changed?
I definitely don't think that a panic is appropriate. @jiaohe Can you provide a code sample that reproduces this issue?
Not all API endpoints are implemented, but there are instructions on how to do this here: https://github.com/andygrunwald/go-jira#call-a-not-implemented-api-endpoint We also ❤️ PR's! You can take a look at some of the...
another example of why using structs for options doesn't work. related to #294 and #200 I think it's valid to remove "omitEmpty". It seems that is it's set to 0,...
Though _just_ removing `omitEmpty` won't fix this problem. Currently, it doesn't seem like we have a way to set a default other than the "zero value" for the integer (0).
@andygrunwald prior to version 2.0, I think we can just start implementing "Functional Options" variants of all methods, and mark the old methods as deprecated.