RowSelectionState should allow undefined values

[marcebdev]

Dealing with a case where a form loads saved values from the BE, then a table is populated showing rows for all the fields. The backend will only return values for fields that are selected, but there may be more optional fields than those selected, and only selected fields get submitted.

This creates an issue because if I'm tying up RowSelectionState to the form state, RowSelectionState will only have selection data some fields (the ones which were saves) however, the schema of optional fields is larger. Since RowSelectionState however, requires all selected rows be defined in the state this makes it a pain to deal with. Either you forgo the built-in state (undesirable) or you have to populate the entire schema into the form, which works, but perhaps makes things more complicated as unregistered values essentially need to be filtered back out, when they could more easily just be unregistered & disabled (aka not part of the form) until selected.

This seems like a somewhat needless requirement as undefined or missing entires could easily just be implicitly false. It feels like the row selection state has been over-engineered to be arbitrarily strict in a way that is limiting.

[marcebdev]

Figured out it was actually complaining about the state object being undefined, even though state should be able to take a undefined value to start with. Ensuring an empty object was always at least present fixed this