This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-11-18
Channels
- # alda (8)
- # aws (1)
- # bangalore-clj (1)
- # beginners (55)
- # boot (114)
- # capetown (2)
- # cljs-dev (51)
- # cljsjs (1)
- # cljsrn (14)
- # clojure (119)
- # clojure-belgium (6)
- # clojure-brasil (9)
- # clojure-conj (2)
- # clojure-greece (1)
- # clojure-korea (2)
- # clojure-poland (12)
- # clojure-russia (64)
- # clojure-spec (12)
- # clojure-uk (60)
- # clojurescript (159)
- # code-reviews (2)
- # component (4)
- # core-matrix (2)
- # cursive (79)
- # datascript (7)
- # datomic (2)
- # defnpodcast (4)
- # events (2)
- # hoplon (13)
- # jobs (2)
- # lein-figwheel (1)
- # off-topic (10)
- # om (42)
- # onyx (60)
- # pedestal (5)
- # perun (7)
- # rdf (4)
- # re-frame (4)
- # reagent (21)
- # ring-swagger (25)
- # schema (1)
- # spacemacs (52)
- # specter (1)
- # utah-clojurians (1)
- # yada (5)
@dm3 zoomed in it looks like it’s not the cells but javelin checking whether things are equal for propagating, does that seem right?
@jumblerg what's the story about set-in!
vs set-in*
?
is set-in!
left there just for backwards compatibility?
the latest commit touching those lines only says "wip" in the commit message
lol, classic commit message
@fiddlerwoaroof im running the latest canary on mac and im still getting a full stack trace:
Uncaught Error: 123 is not ISeqable string.cljs:75
at Object.cljs$core$seq [as seq] (core.cljs:1125)
at cljs.core.map.cljs$core$IFn$_invoke$arity$2 (core.cljs:4491)
at cljs.core.LazySeq.sval (core.cljs:3256)
at cljs.core.LazySeq.cljs$core$ISeqable$_seq$arity$1 (core.cljs:3310)
at cljs$core$seq (core.cljs:1112)
at Function.clojure.string.join.cljs$core$IFn$_invoke$arity$2 (string.cljs:75)
at clojure$string$join (string.cljs:66)
at hoplon$ui$vstr (ui.cljs:82)
at Function.<anonymous> (ui.cljs:708)
at Function.cljs.core.apply.cljs$core$IFn$_invoke$arity$2 (core.cljs:3718)
at cljs$core$apply (core.cljs:3709)
i clicked on the link on the cljs$core$seq (core.cljs:1112)
and at the top of the core.cljs file it does indeed say:
This script is blocked in debugger
yet it's appearing in stackstraces@jumblerg what's going on with assert-noattrs
?
it doesn't seem to be used anymore, neither the attrs?
validator.
does it help composition/extension if non-recognized attributes are just ignored by default?
@jumblerg I've cleaned up our additions/variations on Hoplon UI:
https://github.com/addplus/ui/blob/addplus/src/hoplon/ui.cljs#L659-L783
It adds default value support to forms.
The submit
functions' return values are also used to reset!
form *data*
for convenience.
I put together a super minimalistic showcase for it too:
https://github.com/addplus/ui/blob/addplus/tst/hoplon/forms.cljs
You can try it with boot test
as usual.
(I kept the other demo pages too but they are inactive by default)
This branch also shows how to run Dirac on a custom port and also uses the latest Clojure and ClojureScript versions. You need Google Chrome Canary though to enjoy CLJS REPL within the browser console. (`brew cask install google-chrome-canary`) You have to install the Dirac extension: https://chrome.google.com/webstore/detail/dirac-devtools/kbkdngfljkchidcjpnfcgcokkbhlkogi and start the browser with the remote control port open:
> cat ~/bin/canary
#!/bin/sh
/Applications/Google\ Chrome\ Canary.app/Contents/MacOS/Google\ Chrome\ Canary \
--remote-debugging-port=9222 \
--no-first-run⏎
Then open the Dirac-DevTools with the extension's icon.@micha fyi, related to our conversation the other night https://stackoverflow.com/questions/1776239/are-equal-timeouts-executed-in-order-in-javascript
the call order of setTimeout doesn’t guarantee the execution order in all browsers, although according to the spec it should