/v1/module handles fields parameter in a way that produces single-value arrays

[tsibley]

Compare:

$ curl -fsS https://api.metacpan.org/v0/module/Pod::Cpandoc?fields=distribution
{
   "distribution" : "Pod-Cpandoc"
}

$ curl -fsS https://fastapi.metacpan.org/v1/module/Pod::Cpandoc?fields=distribution
{
   "distribution" : [
      "Pod-Cpandoc"
   ]
}

$ curl -fsS https://fastapi.metacpan.org/v1/module/Pod::Cpandoc
{
   …,
   "distribution" : "Pod-Cpandoc",
   …
}

I'll take a look at this in the next couple days if no one else does.

[ranguard]

I know the 'utility' of flattening arrays is nice, but if it leads to our code having lots of these we should seriously consider just keeping them as arrays all the time

[ranguard]

s/keeping them/keeping results/

[tsibley]

Well, it's a huge PITA for consumers which otherwise would just be able to change endpoints and be done with it.

[tsibley]

For this particular endpoint, we obviously take pains to collapse single-valued arrays, but miss the case when the fields parameter is specified or something. (I haven't looked at the code yet.)

[tsibley]

We can also refactor the controller/model code such that there's only a few places where the output gets filtered through our munger.

[tsibley]

Fixed in #581.