- Issue created by @tr
- Status changed to Needs review
over 1 year ago 1:10am 3 April 2023 - Status changed to Fixed
over 1 year ago 5:54pm 21 April 2023 Automatically closed - issue fixed for 2 weeks with no activity.
Both the block settings for the Barcodes block and the field settings for Barcodes fields take the same parameters, but the text names and descriptions for the settings values are different when they could/should be the same. Likewise, there are many places on the settings form where a sub-optimal input definition is used - for example using a textfield form element for integer input instead of a number form element, and using a string schema type for a boolean variable, etc.
This patch changes the block and field settings to use the same labels and descriptions, and changes the configuration schema to use the correct data types. This ensures that only valid values are entered and stored for all the configuration and block variables and that the user interface is consistent no matter where the barcode is configured.
Fixed
2.0
User interface
Automatically closed - issue fixed for 2 weeks with no activity.