Support 409 for PATCH requests.

[elenacanovi]

As per the RFC specification (https://tools.ietf.org/html/rfc5789#section-2.2), PATCH requests should be able to return 409 in the cases of conflicting state or concurrent modification (my use case btw). However, if I understand correctly the decision graph, this possibility is currently not supported by Liberator if method-patch? is true.

As a possible solution, I tried to add a new decision called patch-to-existing? to replace method-patch? in the false branch of method-delete? and moved method-patch? to the false branch of conflict?. If method-patch? is true then the path leads to patch!, otherwise it leads to method-post? from where the old behaviour is recovered.

I committed this variant to my fork here: elenacanovi@87dc3e5.

[ordnungswidrig]

Thanks, that looks like a missing feature. For make this go into liberator's code base we need tests and docs, too. Please tell me if you want to have a take on it.

[elenacanovi]

Yes, I would be glad to. Is it ok if I prepare a pull request with also test and docs?

[ordnungswidrig]

@elenacanovi Sure! I would love that.

[casseds2]

Hi guys, was there ever any follow up on this issue?

[elenacanovi]

Not from my side, sorry. I'm currently not working on that.

[ordnungswidrig]

@casseds2 I'll try to find the time to merge it. As writren above this requires updates to the documentation and tests which takes some sime.

[casseds2]

Thank you very much Philipp! You're help is greatly appreciated 👌 🙂