bearyinnovative/lili: notifier/bearychat/openapi.go; 3 LoC

Found a possible issue in [bearyinnovative/lili](https://www.github.com/bearyinnovative/lili) at [notifier/bearychat/openapi.go](https://github.com/bearyinnovative/lili/blob/e04d0807d3f42b55cc908c3b6a07b03cae8167c2/notifier/bearychat/openapi.go#L27-L29)

Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first issue it finds, so please do not limit your consideration to the contents of the below message.

> reference to img was used in a composite literal at line 28

[Click here to see the code in its original context.](https://github.com/bearyinnovative/lili/blob/e04d0807d3f42b55cc908c3b6a07b03cae8167c2/notifier/bearychat/openapi.go#L27-L29)

Click here to show the 3 line(s) of Go which triggered the analyzer.

```go
for _, img := range media {
attachment.Images = append(attachment.Images, bc.MessageAttachmentImage{&img})
}

```

Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.

commit ID: e04d0807d3f42b55cc908c3b6a07b03cae8167c2

Read notifier/bearychat/openapi.go at lines 27-29 and inspect how media and attachment.Images are populated. Start by understanding the analyzer's range-variable reference warning; done means the unintended reference is addressed without changing the notifier's expected behavior.

Written by the indexing model from the issue text.