Fork me on GitHub
#untangled
<
2016-11-09
>
wilkerlucio01:11:39

@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)?

wilkerlucio01:11:32

in the current implementation it throws an exception, maybe it's better to validate the call in a pre-condition

mitchelkuijpers16:11:05

Whohoo will be talking about untangled in 1,5 hour

mitchelkuijpers16:11:13

Made my presentation in untangled ^^

mitchelkuijpers16:11:36

Basically ripped of the presentation of @tony.kay 🙂

adambros20:11:53

@wilkerlucio wait how can you respond with anything but a map?

wilkerlucio21:11:02

@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?

tony.kay22:11:53

@wilkerlucio untangled-server 0.7.0-SNAPSHOT just pushed to clojars with your addition

tony.kay22:11:12

@mitchelkuijpers love to know how it went

tony.kay22:11:56

@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.

tony.kay22:11:29

e.g. a precondition failure still looks like an exception, just with a different message (albeit possibly more easily understood)

adambros23:11:49

i thought you have to return {:value …} from a read

adambros23:11:20

but sure, a precondition is fine if im wrong

mitchelkuijpers23:11:16

@tony.kay Presentation went great, people seemed very interested and asked lots of questions (which indicated they understood it) 😁

mitchelkuijpers23:11:04

I tried out the I18n stuff btw, because I wanted to demo it. Cool stuff

tony.kay23:11:46

Cool! The i18n is a little unpolished, but only because we haven't released anything that needed translations yet 😉

mitchelkuijpers23:11:12

Explaining om.next and untangled was hard though

tony.kay23:11:13

the crank is a little rusty on it

tony.kay23:11:35

oh yeah, om next in a single talk is a feat. better to show the basics via untangled I think

tony.kay23:11:48

I just gave @ethangracer that advice for his talk

mitchelkuijpers23:11:41

I have shown only the simple stuff with untangled and some basic db stuff it worked fine

ethangracer23:11:54

Its tough only to talk about Untangled though! So much overlap

mitchelkuijpers23:11:10

Yeah I think its needed

tony.kay23:11:10

you need to hit react, graph db, idents

tony.kay23:11:17

there are a lot of basics

tony.kay23:11:31

Ethan!!!! Welcome home 😉

mitchelkuijpers23:11:41

I did the basics and then some cool demo s

mitchelkuijpers23:11:06

When are you presenting @ethangracer ?

ethangracer23:11:14

It was yesterday!

tony.kay23:11:19

Oh, do tell!

ethangracer23:11:47

I was exhausted after my first day at work so my brain was definitely drained unfortunately

ethangracer23:11:29

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

tony.kay23:11:43

funny how that goes...same experience at PDX

tony.kay23:11:05

new job good? Sold them on Untangled yet?

ethangracer23:11:29

Yeah. I think a lot of people put in on their calendar in case they decide they want to go that day

ethangracer23:11:31

😂 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

tony.kay23:11:12

good deal. Yeah, it's got good minds behind it. The tools are where you'll suffer, I fear

ethangracer23:11:23

Maybe we should port to F# 🤓

tony.kay23:11:40

I'll await the PR