I'm seeing some strange behavior and I can't figure out how to fix it. In my Root component I have a Person and a Week:

But, for some reason two Persons are rendered:

Person has blue background

And I get the following error message in Chrome dev tools console:

If I comment out the (ui-person current-user), reload client so that no Person is showing, and then uncomment, only one Person is rendered, and I don't get any error message.

If I comment out (ui-week selected-week) and reload client, the Person renders as expected, and I don't get any error message

Both the Person/current-user and Week/selected-week are loaded in :started-callback

And neither of them references the other or use any children of the same type

Furthermore the client database looks as I expect it to.

@wilkerlucio I noticed in your talk you used Cursive--have you ever encountered java.lang.IndexOutOfBoundsException: Method code too large! when trying to debug in a project with pathom?

Specifically here: Caused by: Syntax error compiling fn* at (com/wsscode/pathom/connect.cljc:853:38)

@juri could you show more of the code?

@sooheon Yes, gladly. Here's a link to a folder in the repo. As far as I know only the client.cljs in the same folder and ui/root.cljs are relevant here: https://github.com/juripyykko/fulcro-tidsrapport/tree/master/src/main/fulcro_tidsrapport

@juri do you understand how keys work in React? https://reactjs.org/docs/lists-and-keys.html

the error you’re seeing is purely a react error, not related to the parts fulcro does, i.e. it’s UI rendering only

you have :keyfn set on a number of your components, one of them is probably getting props that have their corresponding :db/id missing at some point in the render cycle

perhaps before the initial load

oh lol the fulcro log message right below says it all

the Week component is not getting a value for :week/number

Ask for help~ I’m trying Fulcro+ReactNative . Meet the problem

[fulcro.client.network] Transit decode failed! SyntaxError: JSON Parse error:Unexpected identifier "unexpected"

;; Legal Origins for API request.
 :legal-origins #{"localhost" ""  "192.168.10.192:3000" "192.168.10.192" "" "192.168.10.192:3000/api"}

; [fulcro.client.network :as net]
(defonce app
         (atom
           (fulcro/new-fulcro-client
             :started-callback (fn [app]
                                 (do
                                   (js/console.log "in started-callback")
                                   (df/load app :current-user com.wsscode.multi-timer.components.person/Person)))
             :reconciler-options {:root-render  support/root-render
                                  :root-unmount support/root-unmount}
             :networking {:remote (net/fulcro-http-remote
                                    {:url                ""
                                     :request-middleware net/wrap-fulcro-request})}
             )))

@eric.shao A GET is never handled by Fulcro API (which is what a browser load of the URI will try)

you have to actually test a mutation or load

(or manually encode one into transit+edn in a POST tool)

Also, there is a bug in legal origins, I think…unconfirmed

it’s not much code, so since you’re already there, copy it from Fulcro into your code and see if you can fix it. If you do, please send a PR. I don’t have time to deal with it.

https://github.com/fulcrologic/fulcro/issues/268