I don't have anything to auto refresh the browser, but if you manually refresh then the response should be up to date

I have thought a bit about this though; actually I think it would be pretty easy to set up auto refresh with htmx web sockets

Ah OK. Thanks.

Yes, :reloading messages appear on save and browser refresh shows the changes:

$ ./task dev
starting: [email protected]
starting: [email protected]
starting: [email protected]
Indexing transactions...
Done indexing.
starting: [email protected]
starting: [email protected]
starting: [email protected]
starting: [email protected]
Jetty running on 
starting: [email protected]
starting: [email protected]
starting: [email protected]
starting: [email protected]
System started.
There are 0 users. (This message gets printed every 60 seconds. You can disable it by setting `:com.example/enable-worker false` in config.edn)
CSS done
Go to 
nREPL server started on port 7888 on host localhost - 
 13ms 200 get  /
 31ms 200 get  /css/main.css?t=1648499204556
There are 0 users. (This message gets printed every 60 seconds. You can disable it by setting `:com.example/enable-worker false` in config.edn)
:reloading (com.example.test com.example.ui  com.example.schema com.example.feat.home com.example.feat.worker com.example.repl com.example.feat.auth com.example)
CSS done

Testing com.example.test

Ran 1 tests containing 1 assertions.
0 failures, 0 errors.
There are 0 users. (This message gets printed every 60 seconds. You can disable it by setting `:com.example/enable-worker false` in config.edn)
:reloading (com.example.feat.home com.example)
CSS done

Testing com.example.test

Ran 1 tests containing 1 assertions.
0 failures, 0 errors.
There are 0 users. (This message gets printed every 60 seconds. You can disable it by setting `:com.example/enable-worker false` in config.edn)

+1 on auto-refresh, but would just be ‘experiential sugar’