This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-07-28
Channels
- # admin-announcements (4)
- # beginners (11)
- # boot (148)
- # cider (74)
- # cljs-dev (31)
- # cljsrn (30)
- # clojure (55)
- # clojure-berlin (15)
- # clojure-greece (1)
- # clojure-japan (18)
- # clojure-poland (35)
- # clojure-russia (72)
- # clojure-spec (35)
- # clojure-uk (34)
- # clojurescript (134)
- # cursive (26)
- # datomic (42)
- # dirac (7)
- # editors-rus (1)
- # emacs (17)
- # hoplon (29)
- # jobs-rus (3)
- # juxt (1)
- # luminus (11)
- # off-topic (9)
- # om (66)
- # onyx (49)
- # pedestal (1)
- # perun (19)
- # proton (13)
- # protorepl (5)
- # re-frame (31)
- # reagent (13)
- # ring (2)
- # spacemacs (1)
- # specter (40)
- # spirituality-ethics (2)
- # test-check (41)
- # untangled (7)
- # yada (17)
i had trouble getting start-untangled-support-viewer
to work with our application, it kept failing due to our authentication setup. so i copied the src over and added a request-transform as a parameter to new-untangled-client, and it seems to work now.
maybe its worth allowing an optional set of params to pass through to new-untangled-client?
https://github.com/untangled-web/untangled-client/blob/master/src/untangled/support_viewer.cljs#L56
basically, stubbing network only got us halfway there, as our app still tried to authenticate the user.
@kenbier: The support viewer is very basic. It is really just an Untangled app that loads/views another Untangled app with a historical sequence of app states (it should also be disabling the networking for that embedded app). It is just beyond experimental...as in it still needs a lot of work.