This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-08-02
Channels
- # announcements (14)
- # beginners (133)
- # cider (27)
- # cljs-dev (7)
- # cljsjs (13)
- # clojure (105)
- # clojure-dev (58)
- # clojure-italy (1)
- # clojure-nl (17)
- # clojure-russia (33)
- # clojure-spec (5)
- # clojure-uk (154)
- # clojured (1)
- # clojurescript (35)
- # cloverage (4)
- # cursive (35)
- # datomic (58)
- # duct (8)
- # editors (9)
- # emacs (15)
- # events (1)
- # figwheel (47)
- # figwheel-main (132)
- # hyperfiddle (5)
- # immutant (29)
- # instaparse (21)
- # luminus (3)
- # off-topic (5)
- # onyx (5)
- # overtone (5)
- # pedestal (8)
- # re-frame (7)
- # reagent (6)
- # reitit (3)
- # schema (2)
- # shadow-cljs (178)
- # spacemacs (49)
- # specter (2)
- # sql (1)
- # tools-deps (110)
Was it once the case that you could extend a type to implement IFn
with a variable length arity, as follows:
IFn
(-invoke [this & args]
(apply assoc this args))
but now you have to explicitly define all the arities? I'm seeing the above in a library but getting an errorActually I guess it's just a warning Protocol IFn implements method -invoke with variadic signature (&)
found more info here for any future log readers: https://github.com/reagent-project/reagent/pull/303
Hi All. Can clojurescript port of hiccup
be used alongside re-frame
?
Please excuse cross posting here, but #cljsjs seems to only be populated by PR messages...
@juhoteperi I think you are the most likely to know this - I have now updated the packages for vega, vega-lite, vega-embed and vega-tooltip. These are all versions in support of the final release 3 of vega and release 2 of vega-lite. Newer are now dev rc versions.  10:24 AM @juhoteperi before I commit, should I remove the target directories? Second, should I make four separate commits or all updates in one?
is (:require-macros my.lib.core)
from within the my.lib.core
cljs namespace so that macros can be implicitly :refer
'd now considered idiomatic and generally worth doing when polishing up some library code?
Hey guys, I am having an interesting issue. I am trying to write a macro and in that macro I need to create a namespaced keyword, but I want the keyword to be namespaced to the namespace in which the macro is evaluated, not where it is written? I have tried a bunch of things like trying to find the info in the &env
or trying to abuse the ::key
but no avail. Any thoughts?
This is what I have that currently works, the (-> #'graphql-queries# meta :ns name)
is what I am trying to do but that feels really hacky.
For reference the macro uses another macro (from a library) to gather .graphql files and parse them. Then I want to go through all the found queries and register a re-frame subscription for that query.
So then if in dog.graphql
I define a query called GetDog
I will have a re-frame subscription registered on the keyword :foobar.subs.dog/GetDog
If I use the proposed (:name (:ns &env))
solution I get the following when logging the namespace:
Was this in response to the namespace macro thing? Or the underlying subscription based GraphQL?
Ya it's working out pretty well. I am developing it for my company, it does require some hoops to jump through to integrate Apollo Client into Clojurescript but that is all hidden behind a reagent atom that maps to the ApolloClient's ObserveableQuery. Let me know if you want more info.
we wired up apollo-client to a function that returns a ratom, but components just declare their query in-line basically:
(apollo/watch-query client "query { … }")
I like the idea of separating the queries out to .graphql files, it could allow for some other post-processing steps like validation and other things
@kasuko instead of (-> #'graphql-queries# meta :ns name)
you want the suggested ~(-> &env :ns :name)