fulcro

vasilisk 2025-04-08T15:20:35.991079Z

does rad-routing always enforce this encoded string as query parameter? about?_rp_=WyJeICJd& What if i want some routes to not include it? Can i mix rad-routing with standard dynamic fulcro routing? I am thinking this is probably not a good idea (if it's possible)

tony.kay 2025-04-08T17:50:50.683469Z

you could implement your own version of the history protocol, based on the current one

Eric Dvorsak 2025-04-10T09:55:09.038649Z

I was doing it at some point and regretted it. it's all fine to have clear params in your URLs and even in the path when you do basic crud but it can quickly get out of hand and then you wish you had a map where you can put anything that should be in the url to share a link. That is what this query param is about its just a map of anything you need in the url, including for instance controls on reports

tony.kay 2025-04-10T12:00:34.891219Z

Eric, I’m not sure if you’re for or against. Are you saying “Just leave the parameter and stop being OCD about it?”

Eric Dvorsak 2025-04-10T12:01:34.172319Z

yeah I'm waying I was OCD about it and it brought more issues than anything

Eric Dvorsak 2025-04-10T12:02:31.774259Z

I still have the pretty URLs with the main content ids in clear as part of the path, but even that I might get rid of

tony.kay 2025-04-10T15:45:27.471649Z

I lean the same way: It’s a web application…look at the URLs in gmail. they’ve always got some crazy mess at the end to mark state. The URL isn’t really fully sufficient for the task, but if you actually want a bookmark to some spot in the app that gives you the remote chance of re-establishing the real state, then you need it….and for pages like “about” it seems like a waste of engineering effort to make the URL pretty. I mean, you can still hand out links that are missing the parameters if they don’t matter.

vasilisk 2025-04-10T16:34:48.435099Z

thanks

2025-04-08T19:00:22.972149Z

Has anyone tried react 19 with fulcro? I gave it a go, but it looks like I'm getting errors with regard to findDOMNode at the very least. (We get deprecation warnings in react 18, but in 19 it's removed).

tony.kay 2025-04-08T21:56:50.954919Z

It’s busted. Known issues.

tony.kay 2025-04-08T21:58:21.324519Z

I don’t have time at the moment to fix them. They did the old js ecosystem code motion crap that breaks things. The form field fixes are probably broken. So, you cannot use the new version yet