This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-02-28
Channels
- # announcements (11)
- # babashka (66)
- # beginners (19)
- # calva (4)
- # clj-kondo (26)
- # cljsrn (33)
- # clojure (38)
- # clojure-australia (10)
- # clojure-dev (3)
- # clojurescript (18)
- # conjure (8)
- # data-science (2)
- # datahike (1)
- # datascript (5)
- # defnpodcast (3)
- # emacs (3)
- # events (2)
- # fulcro (17)
- # funcool (66)
- # girouette (28)
- # jobs-discuss (1)
- # lsp (33)
- # malli (1)
- # membrane (11)
- # off-topic (2)
- # practicalli (1)
- # re-frame (141)
- # rewrite-clj (6)
- # sci (1)
- # shadow-cljs (68)
- # sql (5)
- # startup-in-a-month (7)
- # vim (1)
- # xtdb (21)
i have a problem with The required namespace "beicon.impl.rxjs-operators" is not available
The required JS dependency "rxjs/Rx" is not available, it was required by "beicon/impl/rxjs.cljs"
from what I see and read, the library is set up to work with figwheel
, not shadow-cljs
hi @huxley, we are using beicon at https://github.com/penpot/penpot and it works correctly with shadow-cljs, but it needs some tweaks in order to correctly work
about potok, unfortunatelly the documentation is outdated; as I don't expected that the library is heavy used outside from my own projects 😛
because is not very popular way to handle state, and the the people used to have some fear to RX
hehe nice, probably penpot is a good source for knowing how potok+beicon works; the badside is that the project is pretty big that does not help
I'm maintaining >5 years old ecommerce that uses rum
fork rum and datascript
fork. Compared to it penpot
is lovely, simple, organized and super readable 😉
Anyway, don't worry about the documentation, it's all in the code, which is well described.
btw, you are probably the best example of a person suffering from a lisp course 😉 you produce an incredible amount of libraries and you always use your own solutions
hehehe, i'm just curious and try to find a simple solutions for my own problems and challenges; and spend a good amount of time on research on how to improve the currently established solutions
the potok, rumext and okulary is probably a portion of result of this; potok right now is probably 5 years old and it has aged pretty well; we as a team developing penpot did't found real obstacles with the current architecture of state management of the application... I didn't have the same experience with redux, flow and other similar aproaches form the JS world
potok only suffers from the learning curve, because it requires knowing rx pretty well for more advanced stuff
I haven't seen rx/to-atom
used anywhere in the penpot
, and that's the only thing I can think of
@huxley this is something related to documentation 😞 ; look at this line https://github.com/penpot/penpot/blob/develop/frontend/src/app/main/store.cljs#L26
the idea behind this, is that all changes are async, but state should be accessed using synchronous primitives
I also have functions that listen for these differences and based on them return something