Restrict mapping to the handler method to target and triggered element in @HxRequest

[xhaggi]

Closes #79.

[checketts]

Is any work need to ensure this annotation can be composed/subclassed? For example if I wanted to create a @HxTriggeredBy("someId") does this approach allow for that?

[xhaggi]

@checketts thanks for pointing that out. I changed the code from AnnotationUtils.findAnnotation to AnnotatedElementUtils.findMergedAnnotation which supports @AliasFor semantics and annotation hierarchy.

[xhaggi]

@wimdeblauwe as already expressed as an idea, I introduced @HtmxRequestMapping besides @HxRequest and marked @HxRequest as deprecated. Let me know if we should go that way. I will adjust the README afterwards.

[wimdeblauwe]

I am not a fan of @HtmxRequestMapping, because then the code will look like this:

@HtmxRequestMapping("my-button")
@GetMapping("/some-url")
public String doSomething() {
    ...
}

In the case of @GetMapping (which is a @RequestMapping under the hood), the value indicates the URL path the method is available on. In the case of @HtmxRequestMapping, it is not about the URL, but a triggerId or triggerName. @odrotbohm how do you feel about this?

[xhaggi]

IMO it does the same as @RequestMapping but for htmx requests, it maps an htmx request to a handler method, optionally with further restrictions. But we can stick with the current naming. It was just an idea.

[odrotbohm]

I must have lost track on this conversation (PTO currently), but I agree with Wim, that we shouldn't make this a …Mapping annotation. I'm fine with a switch from @Hx… to @Htmx…. Conceptually, what @HxRequest currently does is, is that it qualifies the sibling @…Mapping annotation, replacing a raw headers="…" with a first-class representation of the HTMX concepts that further constrain the mapping. The annotation abstracts the implementation (using HTTP headers) that HTMX uses, and I like that. That said, I don't think we should imply that we introduce a parallel way of mapping, as that's not what we do here.

[xhaggi]

Ok, thanks, then I'll discard it and we'll keep HxRequest.

[xhaggi]

@wimdeblauwe skipped the HtmxRequestMapping idea and addressed all your comments.