zcmiss/qpgame: admin/models/BaseModel.go; 4 LoC

Found a possible issue in [zcmiss/qpgame](https://www.github.com/zcmiss/qpgame) at [admin/models/BaseModel.go](https://github.com/zcmiss/qpgame/blob/f1072a87d5dcfc87e11904477b448582b0703dc0/admin/models/BaseModel.go#L270-L273)

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.

>

[Click here to see the code in its original context.](https://github.com/zcmiss/qpgame/blob/f1072a87d5dcfc87e11904477b448582b0703dc0/admin/models/BaseModel.go#L270-L273)

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

```go
for _, r := range rows {
processRecord(ctx, &r)
processDatetime(&[]string{"created", "updated"}, &r)
}

```

Click here to show extra information the analyzer produced.

```
No path was found through the callgraph that could lead to a function which writes a pointer argument.

No path was found through the callgraph that could lead to a function which passes a pointer to third-party code.

root signature {processRecord 2} was not found in the callgraph; reference was passed directly to third-party code
```

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

Read admin/models/BaseModel.go at lines 270-273 and review the analyzer context included in the issue. Compare the range-loop pointer usage with the linked classification descriptions, then leave the reaction for Bug, Mitigated, or Desirable Behavior that best matches the finding.

Written by the indexing model from the issue text.