This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-11-09
Channels
- # aws (3)
- # bangalore-clj (3)
- # beginners (40)
- # boot (53)
- # cider (1)
- # cljs-dev (124)
- # cljsrn (22)
- # clojure (105)
- # clojure-italy (1)
- # clojure-nl (3)
- # clojure-russia (35)
- # clojure-spec (9)
- # clojure-uk (30)
- # clojurebridge (25)
- # clojurescript (107)
- # datomic (18)
- # dirac (21)
- # events (6)
- # hoplon (29)
- # leiningen (5)
- # off-topic (40)
- # om (17)
- # onyx (25)
- # parinfer (2)
- # pedestal (4)
- # perun (2)
- # planck (1)
- # protorepl (6)
- # re-frame (18)
- # reagent (15)
- # ring-swagger (4)
- # specter (2)
- # test-check (7)
- # testing (3)
- # untangled (45)
- # vim (2)
@tony.kay one other thing, what we should do if the response can't have meta tag (if the response is a string for example)?
in the current implementation it throws an exception, maybe it's better to validate the call in a pre-condition
Whohoo will be talking about untangled in 1,5 hour
Made my presentation in untangled ^^
Basically ripped of the presentation of @tony.kay 🙂
@wilkerlucio wait how can you respond with anything but a map?
@adambros on reads you can respond with any scalar, for example, given the query [:hello]
, a valid response is {:hello "world"}
(so de value returned from the parser call is just the scalar "world"
), I think it's an edge case, maybe don't worth address, what you think?
@wilkerlucio untangled-server 0.7.0-SNAPSHOT just pushed to clojars with your addition
@mitchelkuijpers love to know how it went
@wilkerlucio the response from a read/mutate are always maps aren't they? Oh...I see, the parser pulls the map apart. A precondition isn't much clearer, but probably is a good idea.
e.g. a precondition failure still looks like an exception, just with a different message (albeit possibly more easily understood)
i thought you have to return {:value …}
from a read
but sure, a precondition is fine if im wrong
@tony.kay Presentation went great, people seemed very interested and asked lots of questions (which indicated they understood it) 😁
I tried out the I18n stuff btw, because I wanted to demo it. Cool stuff
Cool! The i18n is a little unpolished, but only because we haven't released anything that needed translations yet 😉
Explaining om.next and untangled was hard though
oh yeah, om next in a single talk is a feat. better to show the basics via untangled I think
I just gave @ethangracer that advice for his talk
I have shown only the simple stuff with untangled and some basic db stuff it worked fine
Its tough only to talk about Untangled though! So much overlap
Yeah I think its needed
I did the basics and then some cool demo s
Glad it went well @mitchelkuijpers !
@tony.kay: thanks 😁
When are you presenting @ethangracer ?
It was yesterday!
I was exhausted after my first day at work so my brain was definitely drained unfortunately
There were a couple people at the end who were interested so we might see a couple new faces in here. Ended up being way less than 80, probably closer to 25
Yeah. I think a lot of people put in on their calendar in case they decide they want to go that day
😂 I wish I could incorporate Untangled but learning F# is literally my full time job at the moment... 8 hours of reading / tutorials / shadowing. It's a cool language
good deal. Yeah, it's got good minds behind it. The tools are where you'll suffer, I fear
Maybe we should port to F# 🤓