This pull request adds the possibility to reuse fields between different content elements. The options are not shared anymore if the feature flag is enabled and columnsOverride is generated for nearly all options next to the already existing possibility to overwrite the label and description.
I executed the following test cases to ensure functionality for the default behavior of sharing fields as well as for the new reusing fields behavior:
Setup "old" installation with the current mask version (8.1.4) and create a content element with all possible field types (as well as inline fields and palettes), update to the new mask version with reusing fields functionality, edit the old content element and add a new one while all options are still shared. Add content and edit it.
Enable the reusing option and migrate the configuration. Checked JSON configuration manually.
Edit the second content element and change all options to something different to ensure the same fields have different options set. Edit content elements and check validation and output.
Repeat tests 1 - 3 but with a "new" installation directly using the new code that contains the functionality of the reusing field.
Set up installation with two content elements and enable reusing functionality, execute mask:restructureReusingFields, and repeat test 3.
Please contact me in case of any questions or remarks.
This pull request adds the possibility to reuse fields between different content elements. The options are not shared anymore if the feature flag is enabled and columnsOverride is generated for nearly all options next to the already existing possibility to overwrite the label and description.
I executed the following test cases to ensure functionality for the default behavior of sharing fields as well as for the new reusing fields behavior:
mask:restructureReusingFields, and repeat test 3.Please contact me in case of any questions or remarks.