[erp5_web_renderjs_ui] Listbox: send checked line's uid list

bt5/erp5_web_renderjs_ui/PathTemplateItem/web_page_module/rjs_gadget_erp5_listbox_js.js

@@ -1256,6 +1256,20 @@
       return queue
         .push(function () {
           data[form_gadget.props.listbox_uid_dict.key] = form_gadget.props.listbox_uid_dict.value;
+
+          // Send the list of checked uids
+          var checked_uid_list = [],
+            all_hide_element_list = form_gadget.element.querySelectorAll(".hide_element"),
+            i;
+          for (i = 0; i < all_hide_element_list.length; i += 1) {
+            if (all_hide_element_list[i].checked) {
+              checked_uid_list.push(all_hide_element_list[i].getAttribute("data-uid"));
+            }
+          }
+          if (checked_uid_list.length) {
+            data['uids:list'] = checked_uid_list;
+          }
+
           if (form_gadget.props.listbox_query_param_json !== undefined) {
             // JSON query parameters are only sent when rendering an ERP5 Form
             data[form_gadget.props.listbox_query_param_json.key] =

[Yusei Tahara]

Hi. I realized that my private patch for listbox is very similar to this commit, but I found one difference here. In my case I use form_gadget.props.listbox_uid_dict.key instead of uid:list. Could you tell me why uid:list is used here? Is it because uid:list is compatible with xhtml style?

[Romain Courteaud]

Yes, this was introduce for compatibility with existing actions, more specifically for the accounting grouping reference action.

[Yusei Tahara]

Thank you for your answer. May I ask one more thing? I would like to know what getContentmethod of field gadget should be, its expected job in ERP5JS. Since I was not sure what getContent should be, I was not able to commit my patch. I thought that my change may be wrong because getContent may be expected as to return all choices, not selected ones only.

[Romain Courteaud]

getContent generates a dictionnary of key/value items expected by the ERP5 Field validator in the REQUEST.

So, the keys really depends on every field implementation.

For the listbox, I'm not aware of any official expected list of keys. So, it is a matter of improving the compatibility of existing actions + adding tests.