velour/catbase: connectors/slackapp/slackApp.go; 10 LoC

Found a possible issue in [velour/catbase](https://www.github.com/velour/catbase) at [connectors/slackapp/slackApp.go](https://github.com/velour/catbase/blob/92da19e5a8fc8974010abf2baef659f3f9ee57ae/connectors/slackapp/slackApp.go#L672-L681)

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 u was used in a composite literal at line 676

[Click here to see the code in its original context.](https://github.com/velour/catbase/blob/92da19e5a8fc8974010abf2baef659f3f9ee57ae/connectors/slackapp/slackApp.go#L672-L681)

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

```go
for _, u := range users {
if u.Name == identifier || u.ID == identifier {
return user.User{
ID: u.ID,
Name: stringForUser(&u),
Admin: false,
Icon: u.Profile.Image192,
}, nil
}
}

```

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: 92da19e5a8fc8974010abf2baef659f3f9ee57ae

Start by reading connectors/slackapp/slackApp.go around lines 672-681 and inspect how the range variable u is passed to stringForUser. Check the analyzer's reported reference and the surrounding user lookup behavior; done means the lookup no longer has the reported range-variable issue and existing project checks still pass.

Written by the indexing model from the issue text.