Sascha Woo

Adding the ExoPlayer `FfmpegAudioRenderer` before the `MediaCodecAudioRenderer` in `TvheadendRenderersFactory#buildAudioRenderers(...)` solves the issue with `audio_version = 3` aka `MimeTypes.AUDIO_MPEG`. It looks like `MediaCodecAudioRenderer` is used to decode `MimeTypes.AUDIO_MPEG` and it fails....

This is supported since version 7.14 of the Java client. https://www.elastic.co/guide/en/elasticsearch/client/java-rest/7.14/java-rest-high-point-in-time.html

My comment was only meant as an indication of when this problem might be resolved.

I can confirm that, and it's really annoying. Since the Servlet 3 specification, web.xml is no longer needed for configuring your web application and has been replaced by annotations. @SummerSun,...

Just a reminder: I have already done the work for this and all other missing response header annotations in PR https://github.com/wimdeblauwe/htmx-spring-boot/pull/67 (Commit for `@HxPush` https://github.com/wimdeblauwe/htmx-spring-boot/pull/67/commits/c2020f56b13d4120bba2ece066e473e28fd9754c). If you want to push...

@tschuehly could you please give us some more insight into your code? Why do you need a prefix and why do you add the `request.getServletPath()` in case `@HxPush` is blank?...

@tschuehly @wimdeblauwe one thing I have changed now is that `@HxPushUrl` has `true` as default, which pushes the fetched URL to the history. The documentation of the header [Hx-Push-Url](https://htmx.org/headers/hx-push-url/) value...

I have made a few improvements to the Javadoc of the annotations.

@wimdeblauwe I added another commit which introduces dedicated annotations `@HxTriggerAfterSettle` and `@HxTriggerAfterSwap` with support for multiple events. Also `@HxTrigger` now supports multiple events. This replaces the `HxTriggerLifecycle` in `@HxTrigger` which...

The reason for this is that all the places where it is used are now code paths that should not be used in the future. Or do you think there...