I think if you're using the :json-verbose output, there's no difference. And if you're using :json output, reusing the same writer will result in proper caching.

Thanks that makes sense!

Well, there's clojure.browser.dom/get-element. But it essentially does the exact same thing.

You could bind stuff you frequently use in your own function to reduce the clutter.

is it required to put annotation into jsdoc meta?

Both approaches seem to work. But I like the :jsdoc one a bit more because it doesn't require repeating the type's name.

you can put it into the regular docs too but then it will appear as part of the regular docs 😛

There's https://github.com/cjsauer/aws-amplify-cljs as an example but is slightly outdated. Honestly the best approach would just be to use native interop with the Amplify library. https://aws-amplify.github.io/docs/js/authentication One little thing to note is that amplify comes with wrappers for the popular frameworks like Vue and React; trying to use those through interop would be unnecessarily confusing. If you stick with the basic library calls on Auth the process should be straightforward and simple for most authentication needs.

oh, I just spotted

did-catch      (collect   :did-catch mixins)        ;; state error info -> state

(let [err (atom nil)]
  (rum/defc error-boundary < {:did-catch
                              (fn [error info]
                                (reset! err info))}
    [& children]
    (if-let [rinfo @err]
      [:pre [:code (pr-str rinfo)]]
      children)))

https://shadow-cljs.github.io/docs/UsersGuide.html#_css_reloading if it is shadow-cljs

interval throws that error. within? is called after interval. It cannot be within?.

I pulled interval out of within and out it in a let binding ‘(let [my-interval (interval (now) (plus (now) (weeks t))])’ then it started working using ‘my-interval’ in ‘within?’. But calling that directly within ‘within?’ It broke ??

Before you had

(interval
          (plus (now) (weeks t))
          (plus (now) (weeks (inc t))))

(interval (now) (plus (now) (weeks t)))

yep, I tried and got a large blurb back

SyntheticEvent {dispatchConfig: {…}, targetInst: FiberNode, dispatchInstances: FiberNode, nativeEvent: Event, _dispatchListeners: ƒ, …} bubbles: (...) cancelable: (...) currentTarget: (...) defaultPrevented: (...) dispatchConfig: null eventPhase: (...) isDefaultPrevented: (...) isPropagationStopped: (...) isTrusted: (...) nativeEvent: (...) target: (...) timeStamp: (...) type: (...) _dispatchInstances: null _dispatchListeners: null _targetInst: null preventDefault: (...) stopPropagation: (...) get bubbles: ƒ () set bubbles: ƒ (val) get cancelable: ƒ () set cancelable: ƒ (val) get currentTarget: ƒ () set currentTarget: ƒ (val) get defaultPrevented: ƒ () set defaultPrevented: ƒ (val) get eventPhase: ƒ () set eventPhase: ƒ (val) get isDefaultPrevented: ƒ () set isDefaultPrevented: ƒ (val) get isPropagationStopped: ƒ () set isPropagationStopped: ƒ (val) get isTrusted: ƒ () set isTrusted: ƒ (val) get nativeEvent: ƒ () set nativeEvent: ƒ (val) get target: ƒ () set target: ƒ (val) get timeStamp: ƒ () set timeStamp: ƒ (val) get type: ƒ () set type: ƒ (val) get preventDefault: ƒ () set preventDefault: ƒ (val) get stopPropagation: ƒ () set stopPropagation: ƒ (val) proto__: Object

OK, try to access target. And it will probably have the value field.

Yep: https://stackoverflow.com/a/47850550/564509

do you find yourself often looking up react solutions to solve reagent problems?

Of course! Because Reagent is but a wrapper on top of React.

In essence, it just allows you to write React applications by using ClojureScript and sticking with more or less idiomatic ClojureScript code.

oh thats helpful! I'll try doing that too, but might need more react skills then

Just note that Reagent is lagging a bit. E.g. AFAIK there's no support for React hooks.

Also, given your last comment under the image, you probably want to set :on-change to something like #(dispatch [:headers-ev/select select-id (.. % -target -value)]) where :headers-ev/select is a re-frame event registered somewhere. I'm not sure whether (.. % -target -value) will work properly in production, where you'd use advanced optimizations. But that's a different question.

yep, here's the solution for logging the change

#(js/console.log (-> % .-target .-value))

Yep. (.. % -target -value) is a shorter form of (-> % .-target .-value).

To try things out to see how they turn into JS you can use http://app.klipse.tech/

that's awesome man.. the way you can interact with objects..

You may like https://github.com/binaryage/cljs-oops It allows using things like (oget x :?a.?b.?c) where none of the fields may exist - it will not throw an error, it will return just nil. Although be sure to use it primarily for data (i.e. JSON). There are various concerns when using it with proper objects due to how stuff gets compiled.

Also, since it's Clojure where we can use macros, (oget x :?a.?b.?c) is actually turned into a minimal JavaScript, without any overhead whatsoever.

haha, definitely on the map, though still some time before I get comfortable with those. 🙂

I assume the absence of the function has something to do with how CLJS is compiled. I've never used alias myself. Out of interest - how do you use it?

Top level of the namespace. (alias 'core 'myapp.core)

I probably misunderstand something. How is it different from (require '[myapp.core :as core])?

Ah, so it doesn't require the existence of the referenced namespace, which is useful for keywords. I see.

Yep!