@dnolen @wildermuthn I just tested out reverting the following commit: https://github.com/clojure/clojurescript/commit/cdaeff298e0f1d410aa5a7b6860232270d287084 in order to fix the Node reloading issue in figwheel

and as expected it fixed the issue

Ok!

I would file issue so I don't forget

coolio

is there a way i can get an atom of a part of an existing atom? for example, if i have an atom that is a map with some key :user, i want to be able to create an atom that represents the value of :user, to control which parts of my app have access to a specific parts of an atom map

atoms don't do this, but reagent atoms allow cursors that behave this way

well, that sounds nice, but does reagent support server side rendering in ring? i am using rum

in cljs since there's no threading, there's no harm in just using multiple atoms though

I haven't used it, and don't know how it compares to rum at all, but it exists https://github.com/reagent-project/reagent-cookbook/tree/master/recipes/reagent-server-rendering

@cjhowe looks like rum has cursors too https://github.com/tonsky/rum

oh, sweet!

I couldn't find a link directly to it, but if you search cursor on that page, looks like it does what you want

yeah, i did that, thanks 😄

http://reagent-project.github.io/docs/master/reagent.core.html#var-cursor

Can anyone tell me what the 😆 symbol refers to?

“:>”

An example https://github.com/seantempesta/cljs-react-navigation/blob/master/examples/re-frame/uiexplorer/src/uiexplorer/scenes/login.cljs#L16

@stuartrexking someone in #reagent can probably answer that

Hi, Given:

(some-func some-arg (fn [err metadata] 
						 (if err(println err) 
						  (println metadata))

I've got a funny feeling about about to learn how core.async works though 🙂

how it works or how to use it?

How to use it... I basically need a way of calling a async function and waiting to built a map from it and ship it in one go... feels a little like an anti-pattern...

@thheller I can’t seem to see anything in the reagent docs. Any hints?

no idea, never used reagent. looks like it has to do with native interop? ie. using a native JS component

Ok. Thanks.

as far as CLJS is concerned it is just a normal keyword

@stuartrexking :> is for using react components.

[:> TitleBar {:controls true :inset true :style {:z-index "1000"
                                                      :position "fixed"
                                                      :top 0}}
      [:> Toolbar {:height              "43"
                   :horizontalAlignment "center"}]]

Yes, but what does that mean? What does it do? What does it refer to?

You can use react components without 😆

Its just syntactic sugar for react-create-class

@crankyadmin you may find this useful, I had a similar question https://stackoverflow.com/questions/39291779/idiomatic-conversion-of-node-js-apis-to-clojurescript

Cheers man... thats exactly what I'm after.

@stuartrexking > You can use react components without 😆 Not quite... See: https://reagent-project.github.io/news/news060-alpha.html "Better interop with native React"

Thanks. I was using adapt-react-class.

@cjhowe in addition to Rum's cursors and derived-atoms you may find interesting this list of libs: https://metametadata.github.io/carry/faq/#is-there-a-way-to-code-a-view-model-if-i-dont-use-reagent For atom "entanglement" there're also these solutions: https://github.com/Frozenlock/entanglement, https://github.com/rymndhng/entangle And here's my solution to "read-only" entanglement: https://github.com/metametadata/carry/blob/143877b3e07f2d530ed0923f2f81cc06a94c5413/src/carry/core.cljc#L54

is there a guide one can follow to publish a cljs package?

Anyone running into a Use of undeclared Var cljs.js/lib warning with 1.9.671? Doesn't happen to me with 1.9.660

@sekao fixed in master

gotcha thanks

:modules enhancements coming very soon. If you feel like giving this a run through https://gist.github.com/swannodette/6150d4213aeb9eba31e03ae522af4425, that would be helpful

the surface is boring, but hides a pretty massive change set - so if you try this also try the build on your own projects

I did a pretty crazy rounding of testing for this - but more is always better

also this guide should make it clear why having a resolve macro now is actually useful 🙂

so, say, electron app might have 1 build that produces 2 files - for main and renderer, right?

@yury.solovyov I don’t know Electron dev that well - but is advanced compilation a thing there?

yes, at least for browser-side

main uses CJS from npm, so might be not as safe to use it there

well, one might not use npm at all, and then yes, should be safe on both

hrm I dunno - there’s nothing really new here in this change

this is just a massive cleanup + ease of use thing

ok, cool anyway

@dnolen reported https://dev.clojure.org/jira/browse/CLJS-2151

@bhauman thanks!

also noted a new relative path problem, which keeps rearing its ugly head

trying to see if its been reported

@bhauman what’s the cause? (or which combo of features)

people have mentioned :libs a couple of times (not :foreign-libs)

yep its in libs

for a single-segment GCL namespace in root of the specified directory

@favila mentioned that but I don’t think he opened an issue

(or something similar)

I will type it up then

@bhauman I’m assuming this case just blows up or something because of bad path computation logic

yep thats it

I've seen some churn around that computation

so a case has been probably missed

making a minimal case to be sure of the specific regression

cool, will make sure some tests come along with this one

🙂

@bhauman just made cljs.loader Figwheel friendly

uh ... pretend I've been under a rock, cljs.loader?

ok module manager

sweet!

@bhauman https://github.com/clojure/clojurescript/commit/5c48ff8c583fcfc1d1c723073e333f9ba65e847a

@bhauman yeah so like shadow-cljs, people can dev projects w/ code splitting the same under :none and :advanced

very very very cool

@dnolen issue filed https://dev.clojure.org/jira/browse/CLJS-2152

@bhauman thanks!

your are very welcome!!