ThomasVNN/Go_skeleton: repo/shop_service_client.go; 5 LoC

Found a possible issue in [ThomasVNN/Go_skeleton](https://www.github.com/ThomasVNN/Go_skeleton) at [repo/shop_service_client.go](https://github.com/ThomasVNN/Go_skeleton/blob/ebb2bf08d29fecd5ef670747a79bd0b091c0ffc2/repo/shop_service_client.go#L69-L73)

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 item is reassigned at line 71

[Click here to see the code in its original context.](https://github.com/ThomasVNN/Go_skeleton/blob/ebb2bf08d29fecd5ef670747a79bd0b091c0ffc2/repo/shop_service_client.go#L69-L73)

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

```go
for _, item := range resp.Data {
if _, ok := mapResp[item.Id]; !ok {
mapResp[item.Id] = &item
}
}

```

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: ebb2bf08d29fecd5ef670747a79bd0b091c0ffc2

Start in repo/shop_service_client.go at the loop around lines 69-73, then inspect how mapResp is consumed and whether its stored pointers must remain distinct. Confirm the intended behavior for each response item and add or run focused checks for that behavior; done means the analyzer finding is resolved without changing the client’s expected results.

Written by the indexing model from the issue text.