hey, having a hard time trying to get an external lib loaded - I’ve made an extern for it, but can’t seem to help the compiler find it - https://github.com/dazld/hello-hdom/blob/master/project.clj < any ideas?

clojure.lang.ExceptionInfo: No such namespace:`

(am giant noob, apologies in advance)

@dazld It is complaining that it can’t find the hdom namespace here, right? https://github.com/dazld/hello-hdom/blob/master/src/hello_hdom/core.cljs#L4

Yeah, I see what you are doing @dazld; you don’t require externs files like that

Ahh, you have hdom set up as a foreign lib, sorry. Misunderstood.

@dazld Since you are using figwheel.main and not cljsbuild, your compiler options would go into, say, dev.cljs.edn, I would imagine

To be honest, if using figwheel.main, I woudln’t bother with lein at all.

Just use deps.edn and clj to drive the whole show.

thanks @mfikes - I’ll try that out 🙂

that’s closer!

now getting:

Compile Warning src/hello_hdom/core.cljs
Use of undeclared Var hello-hdom.core/hdom

I’d like to stick with lein if possible, as this will have some server side elements too

WARNING: JavaScript file found on classpath for library `hdom`, but does not contain a corresponding `goog.provide` declaration: file:/Users/dan/projects/cljs/hello-hdom/foreign/hdom.js

sigh, can’t get this thing to work at all.

sure it’s something small

but.. no idea what

if anyone knows how to fix this - would welcome a PR

thanks for help anyway

@dazld what is hdom? where is that from? https://github.com/thi-ng/umbrella/tree/master/packages/hdom?

it's a js package I'd like to get working with cljs

comes from here... sec

https://github.com/thi-ng/umbrella/blob/master/packages/hdom/README.md

have made a umd build and an extern to work from, but.. yeah.

so did you try either using https://clojurescript.org/guides/webpack or shadow-cljs?

not yet

kind of want to keep it minimal if possible

more minimal than npm install @thi.ng/hdom and (:require ["@thi.ng/hdom" :as hdom])? 😉

no umd build sadly

but! if that works it would be awesome

(generally, that is)

it works in shadow-cljs

it also works via webpack but that requires a bit more work on your end

OK.. it sounds cool, but would love to get this going first

@dazld So it is evidently loading your foreign library now, but you want to reference symbols in it…

You should be able to access it via js/hdom

(have to run, but will check in later)

But, you can make that a little more idiomatic by using :global-exports

See :global-exports here https://clojurescript.org/reference/compiler-options#foreign-libs

Then in your code it should be as simple as

(ns ...
  (:require [hdom]))

(hdom/clearDOM)

@dazld Ahh, you needed to simply put the compiler options directly in the Figwheel compiler options file (not under a :compiler-options key). Sent a PR with that and example of how to use :global-exports

thanks!

Hello, can anybody help me on this stackoverflow post? https://stackoverflow.com/questions/52237173/reagent-uikit-dropdown-use Any help is appreciated 🙂

Is there a quick hack to bring foreign deps into maria.cloud?

I'd like to bring in a js wast interpreter, to test a wast dsl in cljs https://www.maria.cloud/gist/23d9a94fb30ceda55bb62367775e2f73

That's a dsl based on the wah method here: https://github.com/tmcw/wah/blob/master/doc/intro.md

The maria.cloud gist experiments with fixing up the float interpretation using reader tags. Doesn't really work with how macros work out in maria.cloud though.

I've also implemented a version based on https://deque.blog/2017/01/26/catamorph-your-dsl-clojure/ and another that just composes strings on strings. I'd like to get versions of each up on maria.cloud. But it'd be more useful if produced ast forms could be compiled to wasm in browser and tested live.

I'm guessing I can just xhr a dep and inject it in the document

does javascript have namespaces yet?

es6 modules I believe are JS's answer to namespaces, though closures are the old school hack to make things private

hello 👋. has anyone had any success working out how to do snapshot testing in re-frame?

we started using jest snapshot tests in a js react app at work and it has been a revelation - solves so many of the problems i’ve experienced with f/e tests in one fell swoop - and i’m just starting a new cljs/re-frame app and i’d really like to be able to write snapshot tests for it too

my attempts so far have involved using react-test-renderer-shallow like this:

(ns caseworker.core-test
  (:require [cljs.test :refer-macros [deftest testing is]]
            [caseworker.core :as core]
            [caseworker.home.views :as layout]
            [reagent.core :as reagent]))

(deftest snapshot-test
  (testing "snapshot test attempt"
    (is (= []
           (-> (js/ReactShallowRenderer.)
               (.render (-> [home/page]
                            (reagent/as-element))))))))

(ignore the empty vector, just trying to get a failing test so i can see the output printed)

this works to a point, but it doesn’t descend into nested components in the page component, so is of limited utility

this is the output from that test:

#js{:$$typeof #object[#object[Symbol]],
	                :type "div",
	                :key nil,
	                :ref nil,
	                :props #js{:children #js[#js{:$$typeof #object[#object[Symbol]],
	                                             :type #object[#object[Function]],
	                                             :key nil,
	                                             :ref nil,
	                                             :props #js{:argv [#object[#object[Function]]]},
	                                             :_owner nil,
	                                             :_store #js{}}
	                                         #js{:$$typeof #object[#object[Symbol]],
	                                             :type "div",
	                                             :key nil,
	                                             :ref nil,
	                                             :props #js{:className "container-fluid"},
	                                             :_owner nil,
	                                             :_store #js{}}]},
	                :_owner nil,
	                :_store #js{}})

i was wondering if there’s a way to evaluate a reagent component that recursively calls the custom components inside it until you’re left with just “keyword hiccup”, for want of a better way of describing it? haven’t been able to find one yet but not sure what to search for