arucard21

My intent is indeed to make the params part of the matching process as well as the response media type determination. I'll try to illustrate the need for this with...

Thanks for the clear and concise responses. It really helps with ensuring that the message came across well. > Yes, except the client can always use q to influence the...

It doesn't seem like anyone else has been able to give their opinion yet. But I've been trying out this workaround (in Jersey), and it doesn't seem to work that...

@chkal Thanks for your input on this. I appreciate that you think this is worth supporting due to it being explicitly part of the HTTP spec. But I still want...

I recently noticed that this same problem was reported [for Spring MVC](https://github.com/spring-projects/spring-framework/issues/15531). I'm mentioning it because I think it shows that this is a fairly common use case that is...

Is there any update on this? I noticed that the Spring issue has been closed without any changes being implemented for it. But the issue itself does contain a lot...

If I understand correctly, for this specific part of the matching algorithm in the specification, it is optimized for performance, not for accuracy. This means that, by design, it will...

I think it might be fairly easy to do this by adding the curie parameter to the annotation (as you showed) and modifying [this method](https://github.com/openapi-tools/jackson-dataformat-hal/blob/master/src/main/java/io/openapitools/jackson/dataformat/hal/ser/HALBeanSerializer.java#L219) to also allow a `curie`...

The HAL spec does only [specify](https://tools.ietf.org/html/draft-kelly-json-hal-08#section-8.2) to use a `curies` link in the `_links` object. But that `curies` link is intended to define the CURIEs used in the entire document,...

I just had a similar problem after changing time zones. The update button also didn't work, nor did removing and re-adding the widget. But what did work, was to go...