Add 'method' as an expected link attribute

[chrissimon-au]

Add 'method' as an expected link attribute. Appreciate this is non-standard, but works nicely with clients like Halon (https://github.com/LeanKit-Labs/halon#wait-what-are-you-doing-in-addition-to-hal)

There was some debate on the hal spec here about adding method as an optional attribute, which did determine not to add it to the spec... but if you don't mind adding it as a permitted attribute, it would certainly help our use case where we use multiple link relations for different operations on the same resource to explicitly signal which operation is permitted without requiring a separate OPTIONS request.

[naholyr]

I honestly don't see the negative implications it could have, I'd tell : let's try and see if it bothers someone actually ;)
wondering if it should be considered a breaking change?

[chrissimon-au]

I think it shouldn't be a breaking change - the only case I can imagine is if someone was setting the method property on the link and relying on it not being included in the output - seems very unlikely!

[naholyr]

👍 thanks for the input, gonna publish new minor version

[IanIsFluent]

Hi, I'm wondering how one should specify that there are multiple permitted methods - as the examples on https://github.com/LeanKit-Labs/halon#wait-what-are-you-doing-in-addition-to-hal all have a single method specified. I realise it's only allowed, so I can do what I like, but it seems strange to switch between a string and an array when there's 1 vs many methods:

"_links": {"self": {"href":"/x/y",method:"GET"}, "subresource": {"href":"/x/y/z",method:["GET","POST"]} }

I'm assuming you wouldn't split the subresource into two links, one for GET and one for POST?