duniter/WotWizard: src/util/graphQL/write.go; 3 LoC

Found a possible issue in [duniter/WotWizard](https://www.github.com/duniter/WotWizard) at [src/util/graphQL/write.go](https://github.com/duniter/WotWizard/blob/fa3ac5b2a4501b5ad1550eb43576a376bf7c1b69/src/util/graphQL/write.go#L184-L186)

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/duniter/WotWizard/blob/fa3ac5b2a4501b5ad1550eb43576a376bf7c1b69/src/util/graphQL/write.go#L184-L186)

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

```go
for _, dir := range dirs {
WriteDirective(&dir)
}

```

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 {WriteDirective 1} 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: fa3ac5b2a4501b5ad1550eb43576a376bf7c1b69

Start with src/util/graphQL/write.go at lines 184-186 and inspect the WriteDirective function and its callers. Determine whether passing the range-loop variable address can affect behavior, then classify the finding as Bug, Mitigated, or Desirable Behavior; the issue is complete when that classification is supported by the code.

Written by the indexing model from the issue text.