fulcro 2019-06-09 | Slack Archive

tony.kay05:06:00

Fulcro 3.0.0-alpha-3 is on clojars. I’ve ported a number of missing things (functions and nses) over, including server config support, full indexes, improved optimal render, etc. I started a PORTING doc, but it is incomplete, and possibly inaccurate 😜

👌 24

levitanong05:06:01

@tony.kay are there any known issues for making a route target a union?

tony.kay16:06:19

Hm. I cannot think of any, but I ahve not explicitly tested it against unions. The query traversal uses the AST stuff, so I think it should work.

levitanong19:06:05

I’m having odd trouble with errors complaining about my.own.namespace/will-leave not existing when it should be looking into the dynamic-routing namespace. Works properly when i make it a normal query rather than union.

tony.kay02:06:20

well, then it sounds like it has some issue. Not high on my priority list at the moment, but if you can make a repro, feel free to open an issue

levitanong04:06:34

alright, will look into it

souenzzo13:06:11

I'm trying to use fulcro3 but I get Use of undeclared Var edn-query-language.core/query->shallow-ast

tony.kay16:06:34

oh sorry

tony.kay16:06:45

let me cut a snapshot of eql

tony.kay16:06:50

I added a function for performance

👍 4

tony.kay16:06:56

@souenzzo

tony.kay16:06:47

I uploaded 0.0.4-SNAPSHOT to clojars…you’ll have to include that as an explicit dep until the PR is merged.

👍 4

tony.kay16:06:18

:deps    {edn-query-language/eql     {:mvn/version "0.0.4-SNAPSHOT"}

tony.kay16:06:07

I’m pushing alpha-4 to fix the dep…5 mins

tony.kay16:06:46

3.0.0-alpha-4 is on clojars

exit218:06:26

Is there a lein template for fulcro 3 or should I use the existing one and migrate over

geraldodev18:06:29

I guess just pull fulcro3, because that was what I did and not compiler errors (I was expecting them). I removed fulcro-incubator because tony said it became imcompatible, but relevant stuff was backed into fulcro3 already. This time I'm going to to really learn fulcro.

👍 4

tony.kay18:06:51

No template yet. Mostly API compatible..you just need to pull in the right nses

tony.kay18:06:12

but beware it is still alpha…so not a production tool yet. That said, would love more stuff tried out to see where I have bugs

geraldodev19:06:52

please disregard what I said about no error messages on template. There were none because workspace depends on old fulcro and resolves the old code through it

cjmurphy20:06:28

When porting to fulcro3 (alpha 4) I get the error message 'No such var: com.fulcrologic.fulcro.dom/macro-create-element' at the first use of dom in the cljc file (happens to be dom/div) where the require of the namespace is [com.fulcrologic.fulcro.dom :as dom].

tony.kay02:06:28

In CLJC you still need both the server and client dom nses

tony.kay02:06:15

Fulcro 3 cannot solve the issue with clj/cljs fn + macros that the two nses addresses.

cjmurphy03:06:39

`#?(:clj [com.fulcrologic.fulcro.dom-server :as dom] :cljs [com.fulcrologic.fulcro.dom :as dom])` works.

souenzzo23:06:09

where is tempid?

2019-06-09

Channels