[checkmk-commits] [tribe29/checkmk] 8b4b29: Fix ListOfStrings disabling of dropdown after new ...

Branch: refs/heads/master Home: https://github.com/tribe29/checkmk Commit: 8b4b294dd425c8f391217e9f4b2efd3e134ac351 https://github.com/tribe29/checkmk/commit/8b4b294dd425c8f391217e9f4b2efd3e1… Author: Óscar Nájera <oscar.najera(a)tribe29.com> Date: 2021-05-25 (Tue, 25 May 2021) Changed paths: M web/htdocs/js/modules/valuespecs.js Log Message: ----------- Fix ListOfStrings disabling of dropdown after new element Notably on the ConfigHostname valuespec, that when in list of strings the last element would stop working with select2 after selection and creation of a new element. Problem was during copy, it includes not only element id, but select2 has its own id, thus when new element was cloned, it included that id and select2 disabled the previous instance. CMK-7960 Change-Id: Ib7c7c8f1ef191832fe18edd47b15ab71dceeb9d0 Commit: 318331f4a022a8525a7a4c531357f082460507a5 https://github.com/tribe29/checkmk/commit/318331f4a022a8525a7a4c531357f0824… Author: Óscar Nájera <oscar.najera(a)tribe29.com> Date: 2021-05-25 (Tue, 25 May 2021) Changed paths: M cmk/gui/valuespec.py Log Message: ----------- ListOfStrings does not require all fields sequentially filled Previously retrieval of values would stop on first missing value of request. Thus the user cannot leave blank entries. For HTML inputs it was ok, because all fields would be transfered on request, when including the dropdown autocompleters, cleared fields are not transmitted. Thus it is better to inspect the entire request. CMK-7960 Change-Id: I16085ef23468f4fee9aef6d1c95a93c1b5936e23 Compare: https://github.com/tribe29/checkmk/compare/69da7e4ae0d5...318331f4a022