qor/qor-example: models/orders/state_machine.go; 3 LoC

Found a possible issue in [qor/qor-example](https://www.github.com/qor/qor-example) at [models/orders/state_machine.go](https://github.com/qor/qor-example/blob/57633ac0f7fd03fbe855e0f6c29f33ab1ee34ef7/models/orders/state_machine.go#L273-L275)

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/qor/qor-example/blob/57633ac0f7fd03fbe855e0f6c29f33ab1ee34ef7/models/orders/state_machine.go#L273-L275)

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

```go
for _, item := range order.OrderItems {
ItemState.Trigger("return", &item, tx)
}

```

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 {Trigger 3} 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: 57633ac0f7fd03fbe855e0f6c29f33ab1ee34ef7

Start with models/orders/state_machine.go lines 273-275 and inspect the surrounding order-item state transition. Determine whether passing &item from the range loop to ItemState.Trigger is a bug, mitigated, or desirable behavior, then classify the finding using the repository's stated reaction options.

Written by the indexing model from the issue text.