Fork me on GitHub
#untangled
<
2016-04-30
>
brianosaurus00:04:11

How does one include external javascript (mixpanel, fullstory, google analytics) but only conditionally for prod and/or staging (but not dev) ?

mahinshaw01:04:34

@brianosaurus: make a production clubs build and add the necessary files to src-path. Or make a prod index file and add them in the html

mahinshaw01:04:28

Looks like you got some good info from the boot channel. Boot has great functionality for those kinds of processes.

vmarcinko19:04:33

hey all - i have only seen demos of optmistic updates, but what if one wants to do a mutation, and not see any change UI until reload from server shows the results of mutation ?

vmarcinko19:04:40

shoudl I just return

:remote true
from client -side mutations, and do follow-on "app/load" (or "untangled/load" as it is called now) after my transact! line?

mahinshaw21:04:30

A rerender will get scheduled when you call transact, so bypassing the optimistic update seems fruitless. Also, you would need to merge and rerender that component(s) after server update. It's probably wiser to run the optimistic update and use a fallback if the server mutation fails.

currentoor21:04:59

hi, I just updated untangled-datomic to 0.4.8 and now I'm getting this error

Missing dependency :logger of untangled.datomic.impl.components.DatabaseComponent expected in system at :logger

currentoor21:04:31

but the changelog says Added dummy logger to avoid crashes in the notes for 0.4.8

mahinshaw21:04:18

Right, this is a component error. You need to define a logger component on your system. There is one in untangled server I believe.

mahinshaw21:04:03

Actually. There isn't, it's in some of our in house libs, but making one is trivial.

currentoor22:04:13

@mahinshaw: does it have to conform to a protocol?

currentoor22:04:23

is there an example somewhere?

noonian22:04:05

I had this issue and fixed it by just putting an empty map in for the logger :logger {}

noonian22:04:06

component supports plain maps as components so no need to implement a protocol

mahinshaw23:04:18

@currentoor: as long as it implements component:Lifecycle you are good

mahinshaw23:04:08

No problem.

dimiter23:04:26

Anyone here got any input on the following maybe?