Clojurians Log v2

after going back to the basics for about a month, taking another crack at untangled!

expect some wonky questions. 😊

A lot of people find the youtube videos really helpful

https://www.youtube.com/playlist?list=PLVi9lDx-4C_T_gsmBQ_2gztvk6h_Usw6R

I'm on on them as we speak!

into the overall project structure one now.

good deal. The latest whiteboard one is really helpful with server interaction stuff. Not a bad idea to watch that one once you've got the basics down

ah ok will do

and that's what I'm excited about (eventually)... getting the whole stack in place.

your repl reload from cider is much faster than the default 😉

if that comment is directed at me, not sure what you mean. I'm not using CIDER

well, directed at untangled... as you're not a cider user, doesn't help you, but just a happy fyi, I guess.

I think it's totally great your videos (as a result of your personal preferences) use intellij, btw...

because I think the emacs thing is a big blocker for a bunch of potential clojurians.

oh I see. In regular development I rarely need to restart a REPL, so I don't really care about those few seconds. I prefer IntelliJ for the same reason I prefer OSX (over Linux) at this point: lack of a need to fiddle with the settings all the time.

but your getting-started-video project plays very well with cider, which is cool.

I use ideavim for key bindings, and structural editing. I haven't had to touch a config file in years...used to spend 20-30% of my time fiddling...

totally worth the price IMHO

yeah, the videos and project files are meant to work with vim, emacs, spacemacs, IntelliJ

that was something I think is important

I don't like to dictate tools

I'm trying to run (log-app-state) in the repl and getting 'Unable to resolve symbol: log-app-state'... suggestions?

I usually get that when I’m in the clj repl (not the browser repl).

oh boy... lots to learn here...

are you in intellij or emacs?

(I'm not going to get much sympathy probably for emacs/cider issues but hopefully I can hammer through them)

I’m using vim 🙂

ah ok 😉

your earlier clue helped me solve the issue... thanks!

this is certainly not important, but my component does render when at this point:

but it seems you're saying in the Base UI video one needs to add a react-key to the div to show changes to, say, the dom/h4 text.

did something change to enable that?

the video seems to suggest that one must have (dom/div #js {:key react-key} for changes to hot reload.

in fact, all it seems to need is the :ui/react-key in the query function to hot reload. It does not reload without that, in accordance with what you say. But apparently the ui hot reloads for me without any mention of the react-key in the render method.

the react key forces a full dom re-render on hot code reload

it isn't needed for production/regular use

if the data changed, you'll also get a proper re-render

Om optimizes rendering by making sure things do not re-render if the data hasn't changed...but if the key has changed, React will ignore that optimization

having the key in the query will actually cause a root re-render (since that bit of data will have changed)...but children may not rerender if the key isn't on the DOM with a new value

trust me, it is needed for non-trivial hot code reload to work well

aha ok

"you need it" in this case doesn't mean that some cases won't work without it

gotcha

the videos are fantastic, by the way, really having a fantastic Friday due to them.

😀

great, glad to hear that