So I've got a mongoose Model. I'd like to create a couple of reusable clojure functions to wrap some of its methods to make for smooth interop. What tool should I reach for? I'm a bit lost between protocols/methods and the like.

@jayzawrotny the problem with mongoose is that the abstraction it creates are objects, which don't really compose nicely. Creating a protocol over such objects can only help with making clojuric names aka (.fooBar x) to (foo-bar x) and does not really add any value

And the fact that you're lost may be a cue that you don't really need that abstraction

I don't know how your model looks like, but I guess you will want your clojure(script) code to build around verbs instead of nouns, so functions or pathom mutations or re-frame events

And these verbs reflects what tasks you want to do with the domain model at large

In the implementation of these verbs, you can use those ugly js methods anyway, because the "interface" (the verbs and their arguments) are clojuric already :)

To sum up, my point is to skip wrapping mongoose models with clj(s) and go straight to domain modeling

I think you’re right. I was thinking a protocol would be a good choice for creating a (find-one MyModel #js {:id 1234}) but what you pointed out was that it a simple function would work just the same.

Hey folks. I just made a post in the #beginners thread, and I don't want to break any rules if there is one against reposting in a different thread, but it's definitely a beginner question AND a clojurescript question. Just wondering about tooling, if anyone doesn't mind reading my whole question there. Thanks.

Hey guys, any ideas how I could use media queries for material-ui components in reagent? Many thanks in advance.

Found this form in cljs.pprint:

(def ^{:private true}
type-map {"core$future_call" "Future",
          "core$promise" "Promise"})

@p-himik straight copy from clojure.pprint I guess. likely doesn't mean anything in CLJS. https://github.com/clojure/clojure/blob/05a8e8b323042fa043355b716facaed6003af324/src/clj/clojure/pprint/dispatch.clj#L117

I have a few questions about the new :bundle target. I felt it would be helpful if I wrote gist to ask the questions/explain where my questions come from. See https://gist.github.com/athomasoriginal/fd00691bde0be8d9a52c33f3ca968bdc#questions.

Let me know if it’s preferred to just write everything in slack rather than a gist. Further, if anything is unclear or requires minimals, I am happy to provide. Thanks!

hey @tkjone. long-form posts in other mediums is fine IMO

I’m glad you got your firebase example working

your noted benefits of the :bundle target is correct, plus some other things

there’s the JS dependency problem (which you noted) but there’s also many times when we want to feed our ClojureScript code to other tools to allow us to do cool things

for instance, React Native has its own bundler that does a bunch of stuff we don’t want to figure out; so we can use the :bundle target to feed our compiled ClojureScript code to their bundler to easily build mobile apps

for your questions, > When would a user not want to use the `:bundle` target? this is a really good question that I don’t know the answer to immediately. the :bundle target is the latest in the state of the art, so it might be too cutting edge for some. For others, they already have projects that use a different target. I think that if you were building a Node.js app, that using the :bundle target wouldn’t be what you want either; but I’m not really sure about that

> Does the CLJS compiled JS go through optimizations before it gets to webpack? I believe the answer is yes, your CLJS code will be compiled to JS and go through advanced optimizations in release mode

before reaching webpack

> Would it be fair to say that there are times when we would need a `foreign library`, like how the https://github.com/clojure/clojurescript-site/blob/ff54b9490e56f18572427cddf03f0ab3dca893f8/content/guides/webpack.adoc#javascript-dependencies worked, in combination with the `:bundle` target? if your JS code gets included via webpack, then there’s AFAIK no need to write a foreign-lib declaration. If you’re including the JS code in a way that it doesn’t go through webpack, you might need to use the foreign-lib machinery

Good notes and yes, glad to see that there is a way to get the require working. Hopefully it’s not incidental/going to pose problems in the future 🙏

> if your JS code gets included via webpack, then there’s AFAIK no need to write a foreign-lib declaration 100%. my thinking was, before I found the @firebase/app and @firebase/auth solution, that I would have to declare a foreign-lib. Now I see I don’t. So that question was really about a hypothetical…probably not the best way to approach the question because unless it’s a real problem, its speculative.

what does the following error mean?:

Uncaught Error: Vector's key for assoc must be a number.
    at Object.eval [as cljs$core$IAssociative$_assoc$arity$3] (core.cljs:5590)
    at Function.eval [as cljs$core$IFn$_invoke$arity$3] (core.cljs:1977)
    at merge_entry (core.cljs:9104)
    at eval (core.cljs:2459)
    at Function.eval [as cljs$core$IFn$_invoke$arity$3] (core.cljs:2459)
    at Object.eval [as cljs$core$IReduce$_reduce$arity$3] (core.cljs:6786)
    at Function.eval [as cljs$core$IFn$_invoke$arity$3] (core.cljs:2529)
    at merge2 (core.cljs:9106)
    at eval (core.cljs:1503)
    at Function.eval [as cljs$core$IFn$_invoke$arity$4] (core.cljs:1503)