Make json api adapter 'include' option accept an array

[pittst3r]

I'm proposing this change because it just makes more sense (to me). I'm not sure why we're accepting a comma-delimited string and then splitting it into an array instead of just accepting an array in the first place. This still allows a comma-delimited string for legacy reasons. I did not include a test for this on purpose but can add it if you'd like.

I have updated the readme to reflect the usage change. It's pretty straight-forward.

[kurko]

I did not include a test for this on purpose but can add it if you'd like.

I see many tests in there though.

Anyway, could you leave at least one test for render @posts, include: 'authors,comments', without array?

[pittst3r]

Sorry, the way I wrote that was a little confusing. I meant that I did not write tests for the comma-delimited string behavior. But yes, I can add tests for that.

[pittst3r]

@kurko This should be good to go now.

[kurko]

We can’t automatically merge this pull request.

While you rebase this, do you mind adding to the README the stringfied version of include too, instead of just the array version? Something like,

include: "comments,comments.user" is also supported.

[pittst3r]

@kurko K, rebased again and added the additional documentation. 😃

[kurko]

Needs rebase 😁

[pittst3r]

@kurko Rebased again! Please merge quickly before I need to rebase again ahhhhhhh! 😄

[kurko]

hahaha