Possible and intended. Details are in other thread. RAD lets you either define your own elements of rendering (i.e. layout) where the built-in inputs are used, or completely take over rendering (in which case you need to understand Fulcro form-state).

one thing you could do is ignore the warning 😉

jokes aside, what you're doing is what i thought you were supposed to do as well

and ignoring warnings is not the best solution

it worked for a while, with an older RAD

perhaps we should add an invisible flag to controls?

that is an option. But there are surely other possible, perhaps even better solutions? I liked the simplicity of just excluding it from :inputs ...

oh i see, sounds like there shouldn't be a warning if and only if a control is missing from the layout and is marked invisible

the warning is useful for people that want the control on the screen and cant figure out why it's not there

Perhaps :hidden? is better as it is used eg in CSS?

controls have a visibility lambda….and you can ignore the warning…it is just there to keep ppl from complaining to me that their control didn’t show up

https://github.com/fulcrologic/fulcro-rad-semantic-ui/blob/develop/src/main/com/fulcrologic/rad/rendering/semantic_ui/controls/control.cljc#L20

so, either way

IF you have a route parameter for a dynamic router, then you MUST either pre-load the entity in question (before routing), or at least fix the UI graph so that the ident in question is available (i.e. (merge-component! … Person {:person/id id})), otherwise there is nothing to point to

OR

You must use deferred routing and load it in the lambda of deferred

If you’re using RAD, it should be handling that for you

BUT, you don’t want route-to, you want form/edit! (if it is a form)

If you’re trying to route to the display of a person, you’re also probably better off just defining it as a RAD form, and just take over the rendering (and not save it)

or study the RAD form code and state machine and understand how to manage data lifecycles.

Well, I am still troubleshooting my empty report problem and you mentioned there can be a problem with nested deferred routers so I tried to bypass it by making the middle router not using deferring.

As @U08E8UGF7 says. You can use it in many functions such as df/load!, comp/props etc