untangled

NEW CHANNEL: #fulcro
adambros 2017-07-05T06:46:30.401286Z

@tony.kay whats the reason for this fully qualified make-system call?

;; untangled-template/dev/server/user.clj
(defn- init [path]
  {:pre [(not (started? @system))
         (get cfg-paths path)]}
  (when-let [new-system (untangled-template.server/make-system (get cfg-paths path))]
    (reset! system new-system)))
is it refresh related?

tony.kay 2017-07-05T06:47:38.416111Z

doesn’t ring a bell

tony.kay 2017-07-05T06:51:21.466430Z

Updated Things (http://github.com/awkay/untangled): - awkay/untangled : Improved form support is in 1.0.0-beta2-SNAPSHOT (on clojars) - awkay/untangled-template : Sign up page now works (full stack..creates users on server). Uses form support and bootstrap helpers (clone from github).

🙂 2
4
tony.kay 2017-07-05T09:00:49.946474Z

Just updated the CHANGELOG (on develop) to reflect the additions

urbank 2017-07-05T20:16:01.496968Z

When if ever would you advise against using initialAppState ?

tony.kay 2017-07-05T20:27:25.822141Z

@urbank it has a purpose you always want

tony.kay 2017-07-05T20:27:35.826499Z

setting up the app state for the initial UI.

tony.kay 2017-07-05T20:28:13.844062Z

if you mean: which components? : don’t use it on components that are persistent (e.g. come from a server and you load them). It is for setting up UI components for the initial render. E.g. all of the UI tree that needs to be in place before users start using it.

tony.kay 2017-07-05T20:29:32.881764Z

I generally recommend making constructor functions for things that only get created by user events…initial app state is just that: initial UI application state

tony.kay 2017-07-05T20:35:56.062151Z

(by constructor functions, I mean defn of things like make-that-state)

urbank 2017-07-05T20:41:26.213090Z

@tony.kay Got it. Previously I had almost tried to delegate all my state management to initialAppState.

urbank 2017-07-05T21:20:18.235862Z

I'm getting this when requiring untangled.client.core

urbank 2017-07-05T21:20:54.249879Z

[org.clojure/clojure "1.8.0"] [org.clojure/clojurescript "1.9.671"]

urbank 2017-07-05T21:21:14.257850Z

not 1.9 clojure 1.8

urbank 2017-07-05T21:25:46.366226Z

Yeah, it seems to work with 1.9, but then spacemacs cider doesn't. I'll go ask on the clojure channel

wilkerlucio 2017-07-05T21:48:27.884457Z

@urbank Untangled depends on Clojure 1.9, it uses spec already, so you are not going to be able to use it with 1.8

urbank 2017-07-05T21:50:04.918836Z

@wilkerlucio Yeah, figured I'd have to update. Was stalling because only 1.8 immediately worked in spacemacs.

wilkerlucio 2017-07-05T21:51:14.944468Z

you can check with people at #emacs, they might have a solution over there 😉

urbank 2017-07-05T21:59:09.110076Z

@wilkerlucio Thanks, but they already sorted me out in the clojure channel 🙂

wilkerlucio 2017-07-05T22:00:22.136869Z

glad to hear 🙂