are there already some real-world open source om.next projects from which I can learn?

just published Oriens, a Lein / Boot template to scaffold a Compassus application: https://github.com/compassus/oriens run boot -d seancorfield/boot-new new -t oriens -n your-app or lein new oriens your-app to generate a compassus app from this template

@anmonteiro: if I create a project with lein new oriens your-app, I only get a boot project - no leiningen project.clj 😟

I meant Boot template because you can run boot -d seancorfield/boot-new new -t oriens -n your-app

Boot is the build tool for the generated project

it’s right there in the README 🙂

I’m not going to spend any time working on a Lein setup for the generated project, sorry

okok - but you know, I’m on Cursive and like leiningen projects for that reason

no figwheel?

nope, boot-reload does the same thing

and is composable with other Boot tasks

a defonce on app-state would be good

@akiel: sure, PR welcome

@anmonteiro: if I use defonce on the state, I get the same error in your project as I get in mine. The problem is in reconcile! line 1787 in alpha41. The line is ((:render st)) and the problem is that (:render st) is nil. Can you see the same?

@akiel: definitely not seeing that

@anmonteiro: I do the following: lein new oriens my-app, boot dev, change something - in chrome console I see Reload and set-route! messages, change def to defonce - in chrome console I see the following...

@akiel: yeah, hitting that too, I know why

problem is app also needs to be defonced

Can you use any CLJS object as a React key? Does that work?

@anmonteiro: yes I also noticed that a defonce on app works, but than you can’t reload routes and other things

@akiel: should be fixed now, try lein new oriens my-app 🙂

hrm, you might need to delete your local cache though

not sure, just check if it downloads a new one

@anmonteiro: ok works for me - I’ll try this in my project

glad to hear

Put another way: Does anyone know what objects can be used as React keys? Or, more accurately, what React's notion of key equality is?

@peeja sorry no - I never had a need to use custom react keys

@peeja: I think it’s triple-equals equality, so numbers, strings

@anmonteiro: in your solution: init! would not be called in production, I have solved it a bit differently: I prevented reloading of the core namespace, renamed init! into reload! and only do the forceUpdate there

I have all my routeable components in different namspaces

@akiel: init! can be called in production, reloading will never happen

so it just ends up being called once

yes it can be called in production - but will it be?

you need to call it for your app to be set up

ok you can call init! in index.html

yeah, just need to ^:export it

for me it’s simpler to have a non-reloadable core namespace

and you really need the ^:once at routable components otherwise they will not update

@akiel: you can either make everything non-reloadable, and just have the app mount everytime you reload, or make everything reloadable for that workflow to actually work

¯\(ツ)/¯

@anmonteiro: why doesn’t work a forceUpdate on your root component? I tried it. Would be simpler.

@akiel: since props haven’t changed, the shouldComponentUpdate call would fail on the children

but than the mounting has this reconciler bug

I mean, not fail, but return false

if I only change code - do I change props?

no, that’s exactly the point

but if I change something in a subcomponent of a routable component - the forceUpdate also works

ok but that subcomponent has no ^:once - is this the reason?

might be

ok with a ^:once it doesn’t work

so the forceUpdate is not recursive

@akiel: for development purposes you can just use a react-key like (system-time) or something

and put that in props

that’s guaranteed to change

for what I need now - it works fine

is there a way to disable react warnings

only way I know is using the production React