This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-01-04
Channels
- # architecture (13)
- # bangalore-clj (1)
- # beginners (174)
- # boot (25)
- # cider (65)
- # cljs-dev (10)
- # cljsjs (4)
- # cljsrn (3)
- # clojure (169)
- # clojure-berlin (27)
- # clojure-brasil (32)
- # clojure-greece (3)
- # clojure-russia (31)
- # clojure-sg (4)
- # clojure-spec (6)
- # clojure-uk (74)
- # clojurescript (186)
- # code-reviews (5)
- # css (12)
- # cursive (17)
- # datascript (1)
- # datomic (45)
- # dirac (33)
- # funcool (42)
- # hoplon (25)
- # jobs (6)
- # jobs-discuss (114)
- # lambdaisland (6)
- # leiningen (1)
- # luminus (24)
- # off-topic (86)
- # om (13)
- # om-next (14)
- # onyx (75)
- # perun (2)
- # protorepl (19)
- # re-frame (2)
- # reagent (17)
- # ring-swagger (2)
- # rum (1)
- # slack-help (2)
- # specter (31)
- # test-check (5)
- # timbre (1)
- # untangled (34)
- # vim (8)
I'll try to get some time to test the current develop branch against various projects and cut a release in the next couple of days
for the time being, 0.6.2-SNAPSHOT has ssr, but we're technically still on 0.6.1-SNAPSHOT sans ssr
hi all, we have an untangled app that follows the similar pattern provided in the tutorial videos for “tab routing”, app/choose-tab
etc. The issue I am having with this pattern is that I can’t seem to get hash routing to work w/ it correctly. Is there any documentation on this or examples?
If I attach a onClick handler, and not a hash route to my links, things work great. But once I try to move that method into the route method and use a basic hash href I hit a wall.
Tons of documentation and examples. The untangled-cookbook has a working example. The most common errors:
- Putting the ident in the "wrong order". [:type-of-thing ID] is correct, but many people want to do [ID :tab]
when working with tabs...this won't work, because the first ele of the ident is used to pick the query from the UI component
right, I want to be able to use something like secretary and have my tab links be handled in the defroute
calls rather than onClick in the link - if that makes sense?
you just want to do a transact! against the reconciler on the routing event, which is in the app at the :reconciler key.
(defroute listings-activated "/listings/activated" []
(transact! @reconciler [(app/choose-tab {:tab :search :es-type "listing"})
(search/new-query {:listing-status "ACTIVATED"
:time-field :date_created
:es-sort-fields [:date_created]})
:ui/root]))
is an example of what I’m trying to dothat looks roughly right. Sure your mutation is already working (e.g. if you hook up a button it works)
your transaction isn't quoted, meaning you'd actually ask the runtime to run a function called app/choose-tab
Oh I see.. my transact! was actually re-written by the person who setup this project, so it doesn’t need a quote apparently 🙂 @tony.kay
um....there is no way that is right, unless you've built a defroute macro that reinterprets it
(transact! r [(f)])
will try to call f, put the result of f into the vector, then call transact....which will fail miserably
(transact! r '[(f)])
will pass the data structure [(f)]
to transact, which will be parsed and have mutations processed
(f)
is meant to look like a function, but it is used as a data structure, not as an invocation.
The fact that the parser ends up invoking code makes this a little confusing. The data structure (f)
does end up calling something
i love clojure and cljs.
just had to express that.
So I want to accomplish some serverside rendering... I have a core.cljs that renders a nice UI using om.next... I now want to pre-render this UI on the server side in server.clj
... I thought I would make a ui.cljc file and then include it in both the client and the serverside, but there are some quirks between cljs/clj/cljc that I am not well versed in yet... trying to :require om.next :as om
just shows me a lot of unknowns. like it doesn't understand the #js tag (of course) ... I suppose I'll have a closer look at foam + cellophane