fulcro

Book: http://book.fulcrologic.com, Community Resources: https://fulcro-community.github.io/, RAD book at http://book.fulcrologic.com/RAD.html
tony.kay 2020-11-03T00:46:36.008700Z

well, that client code is old client code…the new client code is in the fulcro repo itself (it needs to integrate on the client, without adding inspect as a dep)

Otis van Duijnen Montijn 2020-11-03T09:26:32.011800Z

Thank you for the reply!

tony.kay 2020-11-03T00:46:44.009Z

so, the code you’re working on is no longer part of the tool

tony.kay 2020-11-03T00:48:50.010900Z

when tinkering with inspect, you would work on some demo project in one set of tooling (shadow running on alt port building demo, with Fulcro overridden using local/root) and inspect in another. Changes to client-side comms happen in the demo project env, and changes to inspect happen in the inspect env. It’s quite fun 🙂

tony.kay 2020-11-03T00:49:33.011400Z

and then, you should also be able to use the two repls to work on the two different sides of the comm

tony.kay 2020-11-03T00:49:48.011700Z

look for LANDMARK markers in the inspect code

exit2 2020-11-03T12:54:03.013200Z

When upgrading from Fulcro 2.5.9 to 2.8.13, I get a ton of errors around defsc First it starts off with Uncaught TypeError: _react2.default.createClass is not a function And then most defscs have: Uncaught TypeError: Cannot read property 'any' of undefined

exit2 2020-11-03T12:54:21.013700Z

I’m assuming because after 2.6 things switched to React 16?

xceno 2020-11-03T13:08:28.013800Z

I don't know about fulcro 2x but > property 'any' of undefined sound like you're accessing something that SHOULD be a TS type definition. If you don't have types anywhere in your repo, nevermind

exit2 2020-11-03T15:14:23.014500Z

hmm good tip, let me see

exit2 2020-11-03T15:36:58.014700Z

@rob703 Turns out it has to do with react-bootstrap from cljsjs, looks like I’ll have to do a bunch of refactoring and get rid of it. :(