This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-08-03
Channels
- # admin-announcements (6)
- # announcements (1)
- # beginners (17)
- # boot (69)
- # bristol-clojurians (1)
- # cider (7)
- # cljs-dev (115)
- # clojure (76)
- # clojure-russia (12)
- # clojure-sg (2)
- # clojurescript (152)
- # core-async (2)
- # core-logic (7)
- # cursive (18)
- # datascript (4)
- # datomic (2)
- # hoplon (12)
- # ldnclj (26)
- # off-topic (1)
- # re-frame (48)
- # reagent (6)
Morning
@agile_geek: Morning
@maleghast: OK. Currently in Newcastle train station before catching weekly commuter train to London. You?
@agile_geek: Not too bad, thanks - I am in our HK office trying to stay awake...
Used to work with guys in China (Hangzhou), I was in UK, client was US (NY) so interesting turn around for feedback (24hr min). As I was Tech Lead/Architect in middle made for long days! Early morning ‘stand ups’ with Dev’s & late afternoon/evening with client.
Good morning.
With the luminus creator/maintainer we build a library for managing connections to SQL databases so that you don’t have to pass them around. It uses dynamically bound atoms and it’s the most use of Clojure features I did so far: https://github.com/luminus-framework/conman
@agile_geek: Yep, I have similar issues now maintaining appropriate contact between tech and the European businesses, let alone the Mexico business.
@pupeno: it supports browser javascript right now, and you can shim that to get cljs support (e.g. via adding an externs thing). I have a few customers using it happily with cljs. The sourcemap stuff for sure works great with it.
@malcolmsparks: does that mean in 0.5 i won't need that custom header ?
@mccraigmccraig: in yada 1.0 you'll specify an access-control map in the options and yada will figure out the headers from that - but you can always specify a :headers options if you need full control
@malcolmsparks: cool... will there be big changes to app code for 1.0 ?
not really - the main change is the function is now yada.yada/resource - no kv-args (I've bowed to pressure on that!) - just 2 args - the first is the resource (string, file, atom, etc. or your own Resource-satisfying record) - the second is an option map
content negotiation has changed, it's far more flexible now
how many resources have you created?
currently, just 3, so i shouldn't have any difficulties
1.0 will be released in a couple of weeks I suspect, it's much better than 0.4.3
is it worth me using a 1.0.0-SNAPSHOT ? i expect to be creating a whole bunch more resources over the next couple of weeks
are you using SSE? I expect that's broken in 1.0.0-SNAPSHOT - otherwise give it a test-drive
i'm not using SSE, so i'll try it out