Hi folks, apologies for possibly an obvious question. I'm getting an error as follows trying to write the equivalent of

new PDFJS.DefaultTextLayerFactory()

(new js/PDFJS.DefaultTextLayerFactory)

memo.cljs:70 Uncaught (in promise) TypeError: PDFJS.DefaultTextLayerFactory is not a constructor(…)

the definition of DefaultTextLayerFactory is a prototype, like so:

in https://github.com/mozilla/pdf.js/blob/5aefce6ba6853bee9397b96e7d684521e81f06eb/web/text_layer_builder.js

What is the correct cljs way to invoke this?

It's exported here

hmm. It seems that it's defined like this in pdf.ext.js in the clsjs package:

"PDFPageView": {
        "setPdfPage": function () {},
        "update": function () {},
        "draw": function () {}
    },
    "DefaultTextLayerFactory": {}

is there a flag to use non-minified react w/ cljsjs with advanced optimizations?

@adamw: I’m using the pdfjs package from cljsjs and it seems that there is no such thing as PDFJS.DefaultTextLayerFactory

https://github.com/cljsjs/packages/blob/master/pdfjs/resources/cljsjs/pdfjs/common/pdf.ext.js

@rohit: but yeah, it

@adamw: I saw that as well.

is just a 'thing'. Not a function or anything useful. So no idea how to work with it

@rohit: also it seems like our version of pdfjs is lagging a -looong- way behind pdf/js current

1.1.3 but github is on like 1.4.20

need to learn how this clsjs packaging thing works; I don't understand what the .ext.js file actually does

@adamw: see my screenshot for what I mean

for me PDFJS.DefaultTextLayerFactory is undefined

For packaging help, please use the #C0E66E1H7 channel. I can help you there.

@rohit: thank you!

@rohit: one thing I don't understand. So those definitions in the extern file (PDFPageView/DefaultTextLayerFactory) are from viewer.inc.js, not from pdf.js. This discussion (https://github.com/cljsjs/packages/pull/143) seems to imply that somehow this works, but I would have thought we would need another .extern file for viewer.inc.js, or can we just munge it into one file?

@adamw: lets talk on #C0E66E1H7. Seems to be that the deps.cljs file for it may not be accurate

Hi. I'm in the process of adding specs to a Clojurescript application, and I am seeing some poor performance. Running through the test suite without instrumentation takes about 15 seconds on my laptop. After adding a call to instrument-all in my test runner it takes about 5 minutes. This is after adding specs to only a couple of namespaces. Is this to be expected, or does it indicate that I am doing something wrong?

It seems that higher order functions are the main culprit. For example, an invocation of this function:

(defn- alter-active-word
  [words f]
  (mapv (fn [word]
          (if (active-item? word)
            (f word)
            word))
        words))

(s/fdef alter-active-word
        :args (s/cat :words :command-line/words
                     :f     (s/fspec :args (s/cat :w :command-line/wordwrap)
                                     :ret  :command-line/wordwrap))
        :ret  :command-line/words)

Hi, is there something like alias in cljs? I like to define an alias for a namespace which doesn’t exist only to be able to use shorter namespaced keywords.

anybody know of a way to detect if a PersistentVector is a map entry when using prewalk in cljs?

@akiel: have you tried ::alias/foo or is that only clojure?

@hueyp: yes that works if I define the alias in :require but than the namespace has to exist - I just don’t have the namespace in cljs - it comes from the server

gotcha! dunno~

does anyone know if it’s possible to use https://github.com/dgrnbrg/spyscope in CLJS?

or maybe there’s a way to “inject” stuff with figwheel? then I could use [taoensso.timbre :refer-macros [spy]]?

posted this in #C0620C0C8 but but thought I would add it here too — has anyone used https://github.com/airbnb/enzyme with clojurescript?

@schmandle: to be expected, but I know they are still collecting feedback

@schmandle: at this point probably better to demonstrate what you are doing with clojure.spec and report that on the Clojure mailing list - cljs.spec is more or less a direct port

@akiel: doesn’t exist yet, but there’s some discussion bubbling around that for Clojure, you should make your desire know there - we’re only going to get it if Clojure gets it

(we’re not going to do alias but something at the ns form level is what has been thrown around)

@dnolen: thanks did not know about discussions of this at the ns form level