fulcro

tony.kay 2025-01-01T01:20:23.685589Z

Notice: Fulcro Inspect for Chrome has to be updated soon to remain compatible with Chrome. This new version will require that you upgrade to the latest Fulcro, or use a prior version Fulcro Inspect Electron, or try installing a legacy version of inspect in Chrome or perhaps Chromium. I’ve got approval for release at the extension store, and I plan to release it in the next few days

👀 7
tony.kay 2025-01-15T14:37:24.893669Z

It’s been available via the releases page of the github repo for weeks. My release to store is delayed because I was doing more verification

tony.kay 2025-01-15T15:06:40.880729Z

Thanks for the reminder, though. I pushed it this morning

2025-01-17T09:18:57.390039Z

Thanks! Much appreciated all you do! I haven’t been able to work on my side project as much as I like. But everytime I get the chance to do so, or to study and play around with all the things you’ve made my mind is just blown at what an amazing service you’ve provided to the world with this!

💯 2
tony.kay 2025-01-17T14:59:39.737629Z

Thanks…nice to hear someone notices 😄

tony.kay 2025-01-28T13:46:26.208089Z

I think I still need to add back the “focus inspector” command so that you can focus an example easily…I think that’s all that was left. Well, and the connection bug on restart

tony.kay 2025-01-23T16:01:34.711029Z

I spent a month of my free time doing the rewrite of the internals already 😕

genekim 2025-01-24T00:26:38.233089Z

Totally. I’m so delighted it works!!!!

genekim 2025-01-24T00:26:55.883199Z

Thanks again for the help!

genekim 2025-01-23T00:55:31.199109Z

Thank you for all your amazing work, @tony.kay!!!

➕ 3
🙏 1
tony.kay 2025-01-23T02:27:36.122529Z

See the known bug…you sometimes have to right click on inspect and reload frame after reloading your app

genekim 2025-01-23T02:36:58.767309Z

I think I just ran into this problem — where do I find “Inspect?” Is it the Inspect extension button in the Chrome toolbar? (And what is “reload frame?“) Thank you!

genekim 2025-01-23T02:38:15.020469Z

I see this in Chrome when I click on Fulcro Inspect extension. This is after upgrading fulcro:

com.fulcrologic/fulcro                 {:mvn/version "3.8.1"}

tony.kay 2025-01-23T02:41:45.816669Z

You still do what you used to do

tony.kay 2025-01-23T02:42:08.670709Z

open chrome dev tools. Fulcro Inspect will be one of the tabs (if you have too many there’s a sub-menu)

tony.kay 2025-01-23T02:43:10.773969Z

tony.kay 2025-01-23T02:43:23.330239Z

YOu do need to follow the instructions on the Fulcro Inspect repo README

tony.kay 2025-01-23T02:43:57.230379Z

https://github.com/fulcrologic/fulcro-inspect

tony.kay 2025-01-23T02:44:27.328949Z

so you have to add fulcro inspect in deps.

genekim 2025-01-23T02:44:36.783099Z

I see this, which is new…. first screenshot is what I see when I click Fulcro extension. Second screenshot showing “no app connected.” Same message with Electron app. This is my shadow-cljs.edn segment:

{:preloads   [com.fulcrologic.fulcro.inspect.preload
                                                 ;com.fulcrologic.fulcro.inspect.websocket-preload
                                                 ;com.fulcrologic.devtools.electron-preload
                                                 com.fulcrologic.fulcro.inspect.dom-picker-preload
                                                 holyjak.fulcro-troubleshooting]
                                    :after-load com.example.client/refresh
                                    :watch-dir "resources/public"}

tony.kay 2025-01-23T02:44:40.267799Z

(I think…or maybe fulcro does that already)

tony.kay 2025-01-23T02:44:51.825459Z

no more dom-picker-preload

tony.kay 2025-01-23T02:45:15.132549Z

Just `

com.fulcrologic.devtools.chrome-preload
`

tony.kay 2025-01-23T02:45:42.006929Z

this one is no more too: com.fulcrologic.fulcro.inspect.preload

tony.kay 2025-01-23T02:45:54.074769Z

those just print a console warning telling you they no longer work 😄

genekim 2025-01-23T02:50:17.198839Z

It works! Thank you, Tony!

genekim 2025-01-23T02:56:16.258339Z

Did the Fulcro DOM Inspector get moved or removed? (That was so handy to get the ident/query/props!)

tony.kay 2025-01-23T03:12:10.424859Z

I did not port it forward yet.

tony.kay 2025-01-23T03:12:50.991769Z

the internals of dom-picker are somewhat tied to the internals of React, so it is a point of maintenance…and I just turn on HTML source annotations so I can just look at the source/line, but you’re right that you don’t get the ident/props that way

tony.kay 2025-01-23T03:13:22.536699Z

that said, the current implementation was working, so it is just a matter of hooking it up. I didn’t actually delete the code, just commented it out because I didn’t have time to look at it

timeyyy 2025-01-10T10:22:33.663159Z

it appears `set-active-app` and `dispose-app` where removed from the com.fulcrologic.fulcro.inspect.inspect-client namespace. I picked it up because i'm using workspaces.

tony.kay 2025-01-10T20:43:47.371279Z

ah, I can put them back, could you open an issue?

tony.kay 2025-01-10T20:44:12.654729Z

(I’m not positive I can make them work how they did, but I can at least kill the compiler error)

2025-01-27T13:40:46.556329Z

The inspect in the developers guide supposed to work? (i.e just install the chrome extension?)

tony.kay 2025-01-27T22:12:27.763339Z

Ooops….yes, I actually started a branch for porting, but forgot to finish it 😕

tony.kay 2025-01-27T22:13:25.546639Z

Give me a few days, or perhaps someone with experience can help? I probably won’t get to it very quickly. I really am swamped. You could install the OLD version of Inspect from the releases page of Inspect instead of the chrome web store in the meantime if you’re learning.

2025-01-28T06:28:47.129209Z

🙏🏻 Thanks @tony.kay no rush on my part, I'll install the old version and continue my exploration 🙂

2025-01-15T07:56:28.207029Z

Any idea as to when this will be available?