Fork me on GitHub
Slack Archive

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

2017-05-17

Channels

#boot
<
2017-05-17
>
seancorfield11:05:28

@flyboarder I'm over in England, helping my family deal with my father's passing. I'll be back in the US next week and will try to remember to take a look at that PR then. Feel free to remind me on Tuesday!

mobileink15:05:59

seancorfield: sincere condolences

flyboarder15:05:13

That's ok, I'll have Alan or someone take a look. My apologies and condolences!!

richiardiandrea15:05:02

Condolences Sean

dave11:05:28

i'm sorry for your loss, @seancorfield

djebbz13:05:42

Hello everyone. I've managed to get .cljs source map support in Chrome (finally \o/) with boot-cljs, but it doesn't work with .cljc files... The sources panel of Chromium is empty instead of showing source code. Furthermore, cljs code is not syntax hightlighted. Did I do something wrong ?

kennethkalmer21:05:27

djebbz: did you manage to get around this issue? I’m seeing the same and have tearing my hair out trying to get it to work

djebbz09:05:01

Unfortunately, no...

djebbz09:05:10

I'd be very happy to have a solution if you find it

lwhorton17:05:08

is there anything that would prevent boot from working with clojure 1.9?

lwhorton17:05:27

I’m getting some strange behavior and am having a hard time tracking it down … Call to clojure.core/defn- did not conform to spec: In: [0] val: clj-tuple/conj-tuple fails spec

flyboarder17:05:00

@lwhorton Could you paste the call stack

lwhorton17:05:30

This all started as an attempt to write a simple proxy server, which required at first pandeiro’s boot-http, then httpkit + compojure

lwhorton17:05:56

I’m writing the proxy as a exportable task that can be consumed from a boot file in another project

lwhorton17:05:58

The problem is when trying to consume the lib I keep getting a variety of “did not conform to spec” issues, since I’m trying 1.9 (and using some of the spec features in this project)… some of those warnings were pointing to clj-http‘s improper use of :import. So I swapped over to http kit to try and bypass the bad spec

lwhorton17:05:41

But either some combination of compojure / httpkit / boot-http is failing a 1.9 spec check, or there’s something bigger going on and I’m not sure where to look next

flyboarder17:05:16

that stack suggests it’s either an issue with boot-http or boot-cljsjs

flyboarder17:05:23

probably both

lwhorton17:05:49

I s’pose there’s no way around these other than to patch the libs to be 1.9+ compatible?

lwhorton17:05:41

Oof I’ve been bitten by an alpha

flyboarder17:05:43

or monkey patch the code and do an alter-root-var

flyboarder17:05:33

Why do you need 1.9? is it just for spec?

lwhorton17:05:07

yea, great features in there that’s saving me a ton of time writing reagent views, parsing server responses with conform, testing, etc.

flyboarder17:05:42

ah I see, yeah probably best to submit PR’s then

lwhorton17:05:53

well thanks for saving me from more hours of rabbit-holing

seancorfield22:05:58

FWIW, we've had 1.9 Alphas in production for ages and initially a bunch of libraries had invalid syntax (that earlier Clojure happened to allow) but all the mainstream ones got fixed. I wish library maintainers would be a bit quicker to try the Alphas and update for them.