This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-10-10
Channels
- # aleph (2)
- # arachne (1)
- # beginners (5)
- # boot (33)
- # cider (12)
- # cljs-dev (6)
- # cljsrn (26)
- # clojure (33)
- # clojure-austin (7)
- # clojure-belgium (6)
- # clojure-chicago (1)
- # clojure-dusseldorf (1)
- # clojure-fr (1)
- # clojure-hamburg (1)
- # clojure-nl (11)
- # clojure-portugal (3)
- # clojure-russia (14)
- # clojure-spec (35)
- # clojure-uk (28)
- # clojurescript (49)
- # component (7)
- # core-async (75)
- # cursive (13)
- # datomic (15)
- # dirac (57)
- # emacs (5)
- # events (1)
- # hoplon (34)
- # jobs (2)
- # jobs-discuss (8)
- # lambdaisland (1)
- # lein-figwheel (7)
- # leiningen (3)
- # om (5)
- # onyx (8)
- # re-frame (56)
- # reagent (13)
- # testing (7)
- # untangled (30)
- # vim (51)
- # yada (17)
@stbgz: nice job on https://github.com/eginez/huckleberry, classpath support is definitely needed though. would be a great next step!
@shaunlebron: yeah I've been thinking about that
how does clojure script handle authentication against an api. Im fresh to web dev, so be gentle 😄
@gregnwosu that’s something that’s defined by the requirements of an API 🙂 Is it HTTP Basic Authentication or something, then you would be using functionality available by your chosen lib, i.e. https://github.com/r0man/cljs-http
guys, I'm using figwheel and sidecar, but I keep getting the exceed max line 4096
error which I believe is related to http-kit, does any one knows what might be the problem ?
I am working on a design and have a pretty general question. Is there a shorthand that people find useful for creating documentation for their structure/types? I know there is some using (doc x) written by authors, spec for a more formal approach, core.typed for types. I’m thinking something along the lines of BNF that is concise.
I use Haskell notation with Clojure map/set literals (so the type itself looks like Schema) when designing informally. The final docs are probably best generated from clojure.spec 🙂
@lxsameer it's possibly about cookie size - at least that's where I encountered this problem
@pesterhazy: how did you fix it?
not have such huge cookies
figwheel / cljs analyzer doesn't seem to give very good line number info to where the analyzer error happened when it's inside the body of a macro I called
it just gives the line number to where the macro is called, as oppose to somewhere in the body of the macro
is this the standard state of affairs ? or did I write the macro wrong somehow and it obfuscated the line number info
(defmacro foo [& body] ... (first body) (second body) (third body) ... ) how is this info transmitted
@jasonjckn AFAIK it isn't
it’s why you only get the line number referring to the call
that’s to be expected, and it’s common behavior
@anmonteiro well for some reason my own defui macro is getting far less helpful figwheel analyzer error messages than the original om.next defui macro
@anmonteiro there must be some piece of data i'm loosing along the way 😞
@anmonteiro i did (-> body s/conform ... s/unform) so maybe some macro meta data got lost shrug
@lxsameer that’s the halting problem: use the library in your app, compile everything in advanced mode, exercise your app and then watch if your app halts on a javascript error 😛 it was proven that this cannot by solved by a machine (unless you constrain it with a timeout) ... but easier approach is to ask the library author, if it is human 🙂
@darwin I just read the code of library in question. I could not find any goog.provide
are you speaking about a javascripr library, right? if you want to treat it as a foreign library you should follow this: https://github.com/clojure/clojurescript/wiki/Packaging-Foreign-Dependencies
but that does not guarantee that it will work under advanced compilation, it must be written in google closure compiler compatible-way
@lxsameer ah, sorry, read this instead of the packaging wiki link: https://github.com/clojure/clojurescript/wiki/Compiler-Options#foreign-libs
that packaging page is about producing libraries which will be consumed by other cljs devs
this is my opinion in a nutshell: https://github.com/binaryage/cljs-oops#externs-from-hell
curious if anyone has encountered the compiler error "X is not a relative path" when trying to build with third-party js libs included
@mattsfrey please make something minimal (no 3rd party stuff or tooling please) and open an issue. It may be obvious what is wrong. Thanks.