Type suffix is parsed only after the last semicolon. Eg: name="my[custom::key]:string" will now get the type "string" from the last semicolon. Fixes issue #103
Allow to disable type suffix with the option disableSemicolonTypes: true. Fixes issue #102
Allow to use a different default type parsing function with the option defaultType: "string". This allows more customization in case someone want's to recover some of the functionality that was provided by parseNumbers and similar options that were removed on PR #104
If a data-value-type attribute is provided, then the type specified in the input field is ignored. This allows to specify types using only attributes, in which case semicolons in the field names are not used for parsing. This change is non-backwards compatible, giving precedence to the attributes instead of the type suffixes but it follows a better convention that was already used by other options in the plugin.
Improve how types work with a bunch of changes.
name="my[custom::key]:string"will now get the type "string" from the last semicolon. Fixes issue #103disableSemicolonTypes: true. Fixes issue #102defaultType: "string". This allows more customization in case someone want's to recover some of the functionality that was provided byparseNumbersand similar options that were removed on PR #104data-value-typeattribute is provided, then the type specified in the input field is ignored. This allows to specify types using only attributes, in which case semicolons in the field names are not used for parsing. This change is non-backwards compatible, giving precedence to the attributes instead of the type suffixes but it follows a better convention that was already used by other options in the plugin.