This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-01-15
Channels
- # adventofcode (6)
- # beginners (63)
- # boot (39)
- # cider (25)
- # clara (9)
- # cljs-dev (27)
- # clojure (100)
- # clojure-dev (39)
- # clojure-dusseldorf (7)
- # clojure-italy (32)
- # clojure-russia (23)
- # clojure-spec (28)
- # clojure-uk (51)
- # clojurescript (197)
- # core-async (44)
- # cursive (3)
- # datomic (14)
- # emacs (4)
- # fulcro (27)
- # graphql (23)
- # hoplon (4)
- # jobs (9)
- # juxt (1)
- # leiningen (3)
- # nyc (1)
- # off-topic (6)
- # om (7)
- # onyx (6)
- # parinfer (11)
- # re-frame (23)
- # reagent (15)
- # ring-swagger (1)
- # rum (15)
- # shadow-cljs (37)
- # sql (24)
- # uncomplicate (4)
- # unrepl (17)
Is there a documentation somewhere (maybe in the community?) about how to make a recursive query using om-next?
My goal would be to display a data structure like directory tree/files.
.. a documentation -OR- a working example, that would be good enough.
@vincent.cantin http://book.fulcrologic.com/#_recursive_queries check out this chapter, for fulcro. Tony also wrote up a nice tutorial for om-next before writing fulcro https://awkay.github.io/om-tutorial/#!/om_tutorial.E_State_Reads_and_Parsing if you want to go with vanilla om-next.
Thank you. As I originally started to learn om next, I am still hoping to finish learning it before jumping to another one and having to climb the documentation mountain again. But I am currently doubting if I should insist on om next : I just arrived in the Clojure ecosystem and it is hard to me to distinguish the right path to follow. The community in Slack for om is large but mainly quiet - as quiet as a tree which falls in a forest and nobody hears it. On the other side, fulcro's community is small but active. So I am wondering if I didn't miss an important information somewhere .. did om died? did I miss the 'I give up' notice from its creator?
In any case, I will read the links you gave me. Thank you again.
@vincent.cantin Been there..., also new to clojure and first watched all of the talks on om-next and started learning it 🙂 . From what I understand om-next is conceptually awesome but it was never the intent to be "the next big framework" it's way to flexible, d nolen has a lot of projects that he's working on and om-next was meant to be more of a "blueprint" for people to use as a starting-point for there own "fulcro". Unless you want your appstate to be something like datascript, fulcro seems like a better overall there are a lot of libraries like forms, routing, co-located css, db inspect, etc... not to mention the fact that the model is a lot better (no read parsers, support for pessimistic updates). As for the learning curve you also have a video series for getting started.
@vincent.cantin Been there..., also new to clojure and first watched all of the talks on om-next and started learning it 🙂 . From what I understand om-next is conceptually awesome but it was never the intent to be "the next big framework" it's way to flexible, d nolen has a lot of projects that he's working on and om-next was meant to be more of a "blueprint" for people to use as a starting-point for there own "fulcro". Unless you want your appstate to be something like datascript, fulcro seems like a better overall there are a lot of libraries like forms, routing, co-located css, db inspect, etc... not to mention the fact that the model is a lot better (no read parsers, support for pessimistic updates). As for the learning curve you also have a video series for getting started.