Clojurians
#cljs-dev
<
2016-05-25
>

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

dnolen13:05:02

@bhauman: cool!

bhauman13:05:51

@dnolen: submitted and available for out of band feedback.

bhauman13:05:55

I'm also going to be looking at getting more information into the analysis errors.

bhauman13:05:35

For instance it would be good for each error to have a unique tag ie. :if-form-too-many-arguments

bhauman13:05:34

Also having the form that the error is on (where available) would enable error reporting even further.

bhauman13:05:51

I'm thinking Elm style, using all available information to tell a more complete story about the error.

dnolen13:05:26

@bhauman: something think about but probably not something I’m interested until after we merge all the clojure.spec stuff in (which does macro validation etc.)

dnolen13:05:37

(the tagging each error thing)

dnolen13:05:48

having the form with the error seems fine

dnolen14:05:16

clojure.spec is high priority so there’s a good chance there’ll be lot of progress on Friday

bhauman14:05:52

@dnolen: cool!

dnolen14:05:03

I am interested in whatever is needed to make sure downstream tooling can provide richer error reporting

dnolen14:05:10

so I’m not anti anything here at all

dnolen14:05:33

the Figwheel stuff you’re working on looks really sweet

bhauman14:05:32

@dnolen: Thanks! Having a form with the error, the form can be an optional 4th arg to analyzer/error

dnolen14:05:14

@bhauman: I think probably wise to just make that extra argument a map

dnolen14:05:22

I’m sure there’ll be other ideas of stuff to go there

bhauman14:05:25

absolutely

dnolen14:05:27

:form can be in there

bhauman14:05:54

and maybe :tag

dnolen14:05:54

patch welcome for that

rohit21:05:09

Hi. (cross posting from #C03S1L9DN)

rohit21:05:16

I am experiencing a really strange clojurescript bug. I’ve created a repo explaining it here: https://github.com/ducky427/cljs-bug

rohit21:05:26

Essentially a map I am getting back from converting an edn string to a map using cljs.reader/read-string isn’t behaving like a map at all in the sense of allowing key lookups. and this weirdness only occurs under some very very particular circumstances I’ve been able to able to narrow it down to as little user code as possible. (edited) and its possible to reproduce it without the use of lein or boot or any library Any help would be really appreciated. A co-worker and I have spent better part of 2 days to figure it out and are completely lost now.

rohit23:05:10

follow up on the above issue: i’ve created a repo to reproduce this issue in the browser as well: https://github.com/ducky427/cljs-bug-browser

rohit23:05:51

I’ve tried using tools.reader instead of cljs.reader to no effect.