You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug 🐛
This bug is a miss in that the request body to POST /wiki/api/v2/pages may include parentId but go-atlassian does not include it in models.PageCreatePayloadScheme.
To Reproduce 🚧
Steps to reproduce the behavior:
Create a new models.PageCreatePayloadScheme
Observe no ParentID member.
Expected behavior ✅
A clear and concise description of what you expected to happen.
Expected a ParentID member.
Screenshots 📄
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Code snippet
package main
import (
"context""github.com/ctreminiom/go-atlassian/jira""log""os"
)
funcmain() {
var (
host=os.Getenv("HOST")
mail=os.Getenv("MAIL")
token=os.Getenv("TOKEN")
)
jiraCloud, err:=jira.New(nil, host)
iferr!=nil {
return
}
jiraCloud.Auth.SetBasicAuth(mail, token)
jiraCloud.Auth.SetUserAgent("curl/7.54.0")
// Steps to reproducepayload:=&models.PageCreatePayloadScheme{
SpaceID: 203718658,
Status: "current",
Title: "Page create title test",
ParentID: 12345678, // <- Compile error: "Unknown field 'ParentID' in struct literal"
}
}
The text was updated successfully, but these errors were encountered:
go-atlassian version
Most Recent (v1.5.0)
go-atlassian component
Describe the bug 🐛
This bug is a miss in that the request body to
POST /wiki/api/v2/pages
may includeparentId
butgo-atlassian
does not include it inmodels.PageCreatePayloadScheme
.To Reproduce 🚧
Steps to reproduce the behavior:
models.PageCreatePayloadScheme
ParentID
member.Expected behavior ✅
A clear and concise description of what you expected to happen.
Expected a
ParentID
member.Screenshots 📄
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Code snippet
The text was updated successfully, but these errors were encountered: