Hi @ashwanthkumar ,
I installed slack-go-webhook to my project by dep command.
The dep command installed slack-go-webhook-v0.2.
My projects uses Attachment.MarkdownIn, but v0.2 does not include it, and go build failed.

Please add v0.3 (or other new version number) tag to the GitHub repository if you don't have any problems.
Thank you.

Hi i was not able to add Color in the Attachment can you please help on this

how do you add Color to slack message if fail i want to mark it red

attachment := slack.Attachment{
Color: "#1766ff",
}

it was throwing error
`cannot use "red" (untyped string constant) as *string value in struct literalcompiler[IncompatibleAssign](https://pkg.go.dev/golang.org/x/tools/internal/typesinternal?utm_source%3Dgopls#IncompatibleAs

sign)

`

Please create a new version tag, because package control like glide detecting version by default.
It seems your tag 0.1 have old code(Payload is function).

I do not understand why returning a slice of errors is useful in Send(). Especially if, in the end, we only return a slice with a single error:

It is less convenient to handle errors gracefully in the caller:

errs := slack.Send(webhook, proxy, payload)
for _, e := range errs {
    log.Error(err)
}

// or if you know there can be only a single error in the slice:

if errs := slack.Send(webhook, proxy, payload); len(errs) > 0 {
    log.Error(errs[0])
}

I was thinking about trying to add threading support to the library, are you interested in this if I do so? Would be really nice to be able to thread messages properly, especially when using this in the context of automated outbound notifications (to slack) and automated responses to these notifications (also to slack).

Have you explored this at all? Looks like it would be doable as it's all optional.

Hello,

First of all, thanks for the library!
Would it be possible to add a support mrkdwn_in in the library? It'd help to post e.g. stack traces

Best,
Rafal

Hi, not sure but seems like those two properties are unused?