This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-01-31
Channels
- # aatree (1)
- # admin-announcements (3)
- # aws (3)
- # beginners (36)
- # boot (227)
- # cljsrn (27)
- # clojure (57)
- # clojure-czech (6)
- # clojure-miami (8)
- # clojure-poland (17)
- # clojure-russia (113)
- # clojurescript (9)
- # community-development (1)
- # core-async (11)
- # core-matrix (2)
- # core-typed (3)
- # cursive (3)
- # datomic (5)
- # editors (40)
- # emacs (6)
- # heroku (1)
- # hoplon (50)
- # incanter (1)
- # ldnclj (4)
- # luminus (3)
- # mount (1)
- # om (132)
- # onyx (5)
- # proton (3)
- # re-frame (5)
- # spacemacs (1)
- # testing (12)
- # yada (6)
@mateusz-fiolka: You can use figwheel for node development. Though have also used a combination of cljs watch and file watcher to restart the node process in the past.
I’ve just created place selection input based on Google Places API using re-frame (which is based on Reagent) and wonder if it would make any sense to extract it as a library for others to use. It’s quiet a simple thing, yet takes up to a few hours to implement. The only concern I have is that being built with re-frame it is quite specific, in comparison to ‘plain’ Reagent or Om.
@pshk4r: Sounds very useful to me. Would be nice if it was generalized enough to be used in Reagent and Om as well. Or appropriate variations for those frameworks.
What am I missing ? I'm using assert defensively, but sometimes the messages do not appear on developer's console. This specific case was one. Should I surround each potential clause with a try catch ?
hi all, i’m working with a js library that uses promises. i’m trying to understand how i’d interact with those promises inside of clojurescript.