Tomasz Kucharzyk

@geoand Quarkus shouldn't have anything specific to htmx. It should be generic feature. End user will decide how to use it

Wouldn’t it be better to create only support for conditional routes in resteasy. With such flexible foundation everybody could create solution for him with few lines of code. After that...

I can confirm this issue. I don't think it is intended. Problem is described at stackoverflow: https://stackoverflow.com/questions/9445588/re-open-last-closed-tab-causing-to-show-last-ajax-request-content After restoring tab browser shows last cached ajax response. You can use Cache-Control...

After some rethink I thought about the downsides. We don't want completely disable cache. '''/sample? Hx-boosted=true''' would be better solution. Address is different so We don't break re-opening tab but...

@oliverhanappi @David-Guillot probably it won’t work. After reopening closed tab it will be returned from browser cache without hitting sever.

There are two solutions. 1. Do not cache fragments by sending correct cache headers from servers. 2. Modify htmx to add query param (for example ?fragment=true to url when requesting...

Temporary solution for this exception may be additional 'catch-all' route but It do not work well with useraccounts package ``` javascript Router.route("/(.*)", { name: "notFound" }); ```

I have the same issues while running angular-cli via YarnTask from gradle After killing gradle with CTRL+C angular-cli is still running

I've found temporary solution. Disabling gradle deamon fix this issue. Just create following gradle.properties file in project directory ``` org.gradle.daemon=false ``` With deamon disabled everything works allright. With deamon enabled...

I am facing the same issue. After upgrade my tests are failing randomly saying that one of the parameters was not supplied. This bug was introduced somewhere after 1.0.0.RELEASE and...