hey

is it normal that when my code reloads I get 2 rerender console messages

I get 2 messages each code reload

[ 32.447s] [om.next] RERENDER: NOTE: If your UI doesn't change, make sure you query for :ui/react-key on your Root and embed that as :key in your top-level DOM element

yes, I’ve seen that. I think I have the template set up where it triggers the refresh twice by accident. It is harmless, though, so I haven’t bothered to fix it.

ok

could also get that when using devcards, since multiple cards running apps could be refreshing.

hm is it a problem if my initial state uses idents?

should I denormalize my initial state?

Use InitialAppState….it is much much much easier in the long run. Hand-coded initial state works just like stock: atom is assumed to be pre-normalized by you, map is tree that will get auto-normalized.

unions for ui routing are also automatically handled by initial app state mechanism, so it should really work for like 99% of initial app state needs.

If you are using the initial-state mechanism, then it is incorrect to use idents

because you are making a tree, and that will confuse things.

it is ok to have duplicate state in your initial state mechanism tree…the copies will get merged into the same final table in the client db…that is harmless

(e.g. you need two UI components to initially point at the same normalized thing)

ok

@tony.kay Should this be checking to see if fallbacks have run before calling om/force-root-render!? https://github.com/fulcrologic/fulcro/blob/master/src/main/fulcro/client/impl/data_fetch.cljc#L427

I'll try denormalizing

because right now it doesn't work

I think that should be (when @ran-fallbacks (om/force-root-render! reconciler)) right?

now it just fails to create idents

@roklenarcic All of that stuff is well-tested, so I’m not sure if you’re trying to ask a question or just venting 🙂

@gardnervickers You mean you’d like to not force a rerender if there were not fallbacks? I think I removed that because there is already short-circuiting in React for doing much work, and errors are not common

changes are present: global loading marker, other loading markers

Gotcha

That makes sense

When I try to build the test build with figwheel I get this error> > WARNING: Bad method signature in protocol implementation, fcn/FulcroNetwork start does not declare arity 2 at line 522 resources/public/js/test/fulcro_spec/renderer.cljs Any ideas?

When I try to load http://localhost:3449/fulcro-spec-client-tests.html, I see an exception with message Component :test/renderer was nil in system; maybe it returned nil from start or stop

and the html page just shows Loading “js/test/test.js”, if you need to name that something else (conflicts?) make your own test html file

is there some way in REPL to see if normalized tables have been created

nvm, figured it out

oh cool, we’re at 100 😄

@roklenarcic You are aware of the new video series I’ve been building? That can be very helpful for getting started, perhaps as much or moreso than the docs. Esp the core concepts ones.

https://www.youtube.com/playlist?list=PLVi9lDx-4C_Rwb8LUwW4AdjAu-39PHgEE

Is there any documentation on how to use the stuff in the fulcro.client.routing namespace?

in the dev guide

and in doc strings

and in the template as an example

and there is an Untangled YouTube video that shows how it was basically designed

the dynamic routing is shown in a demo in the demos on the fulcro repo itself

Didn't realize the devguide was seperate documentation. Thanks!

in

(let [{:keys (person/name person/age) (om/props this)}])

not much there…you ahve a typo

(let [{:keys [a b]} (om/props this)] …)

would extract the values of keys :a and :b from the map returned by props into local symbls a and b

^ is essentially sugar for (let [{a :a, b :b} (om/props this)] ...), @jhorwitz