kee-frame
kee-frame copied to clipboard
re-frame with batteries included
Having your app live in a subdirectory will cause the hash to include it when the app navigates to a different route. Say my app lives here: `www.myapp.com/myappliveshere` If I...
Looking at the code the `:scroll` option to `kee-frame.core/start!` seems to be what matters and requiring `kee-frame.scroll` seems to be a no-op because it's already required by `kee-frame.router`.
Will help make signatures clearer, and give clearer error messages.
Would it be possible to make interop/render-root for the new api `createRoot` of React 18?
Does two things: - Adjusts the wording in the README to better reflect current code - Fix a bug where pages don't scroll if there's no ajax request made It...
I would like to be able to deploy kee-frame applications on github project pages which typically look like yourname.github.io/your-project. This does not work at all unless you disable route hashing....
Would it be possible to add an `:on-navigate` property to the `:navigate-to` effect so that we could dispatch more events only and only if navigation is complete?
I am trying to streamline an application and noticed in the shadow-cljs build report that kee-frame is relying on some heavy spec dependencies. I've been able to overwrite expound with...