What do you think about allowing the server to force a link to be an array

[chadkouse]

For example - when you have a link relation that is sometimes an array, and sometimes a single link - it can confuse clients to have to figure out when it is and when it isn't. I have built the code to support a 3rd argument to the Resource.link method which is an optional boolean value to indicate forcing an array. If you think it's useful I'll send a pull request.

Here's my work: chadkouse@8e206c3

Thanks

[jpbochi]

Looks interesting.

However, I'm not a fond of receiving boolean parameters for this kind of thing. On something like resource.link('employee', '/one', true) the true there doesn't give you any clue about its meaning.

How about, for example, resource.link('employee', ['/one'])? It is more explicit about the array, and it would also be a short-cut for adding several links with the same relation.

Since you have a fork of my repo, you can implement it there and pretty easily created a pull request with the changes from your repo to mine. If you do that, naturally, add some unit tests to it.

[chadkouse]

Now that I'm looking at it again, maybe if you do resource.link('employee', ['/one', '/two']) it should add 2 links with the same rel?

[chadkouse]

I updated the PR to do that ☝️

[chadkouse]

(just realized that's what you were talking about in your initial comment...)

[chadkouse]

I updated #8 and tightened / cleaned it up - see what you guys think.