perfect thank you!

This is a very general question. The main thing to remember is that the UI is a function of the Fulcro client DB (`view = fn(data)`). The short answer is that you update your UI by updating the database using mutations (`transact!`) and loads (`merge!`, load!).

If you haven't already, I recommend checking out https://fulcro-community.github.io/guides/tutorial-minimalist-fulcro/

thank you, I actually found my answer here, I was looking for uism/asm-ident

Ah, I guess I misunderstood a little. Good luck 🙂

Why would you want to do that?

Because I need to retrieve the uism/asm-ident corresponding to that component ident.

{:query         (fn [] [:connect/id :connect/name
                         (uism/asm-ident [:connect/id id])])}

but I guess this is circular reasoning, right?

(from the docs: https://book.fulcrologic.com/#_looking_at_the_running_instance)

I think you should be identifying your asm by keyword there. The ASM id won't be the same as the current component id, I don't think..

It is, I initialize it with:

(uism/begin! this providers/connect
                                        [:connect/id id]
                                        {:actor/connect-button this})

the id is [:connect/id id]

Am I not allowed to do that? If not, how do I make parametrized state machines?

(uism/begin! app-or-component machine-def instance-id actor-map)

    Installs an instance of a state machine (to be known as instance-id, an arbitrary keyword), based on the definition in machine-def, into Fulcro’s state and sends the ::uism/started event.

oh yeah, a keyword

that's very limiting, though

I think what you want is to add an actor to that state machine and have that actor correspond to your component, rather than coupling your SM to your UI at the top level.

Yes, but I have multiple instances of the same component that each need to access their own SM instance

should I open a feature request?

I think you should try to describe what you're trying to do in a bit more detail and see if someone with a bit more experience can help you out.

okay, thank you.

You can have multiple instances of a component, each with its own instance of the SM, the component instance being an actor in the uism.

It may be better to explain more of what you’re trying to achieve but you could possibly use ident joins. I’m not sure if there is a section in the docs for it but if you search for ident join Some info on link queries which are a kind of special case ident join https://book.fulcrologic.com/#_link_queries

I think this is the section in the docs that talk about them https://book.fulcrologic.com/#_idents_as_a_query_element

Thank you, I'll look for that

BTW initial state is only one source of data. Merge or df/load is another. To access data not belonging to the data entity, use Ident or Link queries - see https://blog.jakubholy.net/2020/fulcro-divergent-ui-data/ But make sure you understand Fulcro well and are not trying to force an incorrect solution to a need. As suggested elsewhere, the minimalist tutorial and its exercises should help.

@U0111PVCS8P What I think is important for you to understand is, that the queries of components are not run against a database on their own. It is not like your components query for data and get "their own data" delivered straight from the database. Instead, queries are composed together and in the end there is only one query run against one (normalized) database. This query is located in your "Root Component". In the end, your root component gets a single tree of data, that it feeds down your render functions.

This, for example, doesn't work:

(def db 
  {:foo "bar"})

(defsc B [{:keys [foo]} _]
 {:query [:foo]}
 (dom/p "foo"))

(def ui-b (comp/factory B))

(defsc Root [_ _]
 {:query []}
 (ui-b))

See the diagram https://fulcro-community.github.io/guides/tutorial-minimalist-fulcro/#_components_query for a visual of the above explanation.