fulcro

Book: http://book.fulcrologic.com, Community Resources: https://fulcro-community.github.io/, RAD book at http://book.fulcrologic.com/RAD.html
tony.kay 2021-03-07T04:53:07.195600Z

Not easily. Many of the macros in Fulcro expect the JVM because of SSR support, and would all have to be ported to bootstrapped cljs. It of course is possible, but it would need to be an actual fork, since it would be way too much work to try to maintain bootstrapped cljs support while also not breaking functionality.

tony.kay 2021-03-07T04:54:31.195800Z

But then maintaining a fork is quite a pain

Jakub Holý 2021-03-07T07:47:39.196500Z

I see. Thank you!

👍 1
Jakub Holý 2021-03-07T16:40:42.199300Z

🙏 Pls help me test the new, compile-time check of query validity in Fulcro, especially if you have any non-trivial app (already tested on RAD-demo) - simply change your fulcro dependency to {:git/url "<https://github.com/holyjak/fulcro.git>", :sha "dae6a795eee6fcc5e6bb3df9872b54f26b980fd6"} (which is latest Fulcro develop + 1 commit) and restart shadow-cljs (if you are running the backend, you can likely leave it be, this change is only relevant for the frontend). Share whether it works for you! 🙏 To test, add eg an empty {} into a query. (Beware - the check doesn't work for queries inside lambdas)

Jakub Holý 2021-03-07T18:04:23.201Z

You can also add to your deps.edn this alias

:aliases {:jh/fulcro {:override-deps {com.fulcrologic/fulcro {:git/url "<https://github.com/holyjak/fulcro.git>", :sha "dae6a795eee6fcc5e6bb3df9872b54f26b980fd6"}}}
and then activate it in shadow-cljs.edn :
{:deps {:aliases [:dev :test :jh/fulcro]} ...

tony.kay 2021-03-07T19:12:18.201700Z

You don’t have to modify shadow-cljs.edn, you can just add -A:jh/fulcro at the command line shadow-cljs -A:jh/fulcro server

❤️ 1
tony.kay 2021-03-07T19:22:15.201900Z

I can confirm this does not break a project that has 60kloc. One minor improvement, which I’ll mention in the issue