fulcro

Book: http://book.fulcrologic.com, Community Resources: https://fulcro-community.github.io/, RAD book at http://book.fulcrologic.com/RAD.html
tony.kay 2021-02-15T02:10:26.403200Z

You need to understand that queries are a composition from root of your data graph. The only way a component receives data is one of the following: 1. It is well-connected in the data graph 2. You use “floating roots” 3. The component is well-connected AND it uses a link query Components that are not floating roots cannot query for arbitrary data and just expect to get it. I’m working on explaining this in gory detail in the new Grokking Fulcro video series, but it is well-covered in the book

2021-02-15T02:41:06.403400Z

Ah-ha! After realizing that a floating root was not what I wanted and it was my intention to have this data well connected, I realized that I needed to create some sort of relationship between an account and the link to that account pointing to the same ident. Once I did that, it's working the way I want.

stuartrexking 2021-02-15T06:57:00.405400Z

I want to mark some form fields to always be complete. Do I mark them complete in componentDidMount, or do I mark the entire form complete on submit and do my submit logic alongside the mark-complete! in a pessimistic transaction?

stuartrexking 2021-02-15T06:57:35.406Z

Or do I just remove fields from the form that don’t need to be completed and validated against at all.

stuartrexking 2021-02-15T06:59:36.406700Z

I’m leaning towards just marking the fields complete that are always complete (like a checkbox) on componentDidMount.

Jakub Holý 2021-02-15T14:11:45.407300Z

I guess u could also simply change the data directly when you add fs config to it, ie. in pre-merge or a mutation, whatever you use to load it.

stuartrexking 2021-02-15T23:55:32.409800Z

This is what I went for. I clear my form on load and set the field to completed.