Fork me on GitHub
#fulcro
<
2020-11-03
>
tony.kay00:11:36

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 Montijn09:11:32

Thank you for the reply!

tony.kay00:11:44

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

tony.kay00:11:50

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.kay00:11:33

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

tony.kay00:11:48

look for LANDMARK markers in the inspect code

njj12:11:03

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

xceno13:11:28

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

njj15:11:23

hmm good tip, let me see

njj15:11:58

@U012ADU90SW 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. :(

njj12:11:21

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