Title: Input Mask Proposal
Status: Current
Rather than include an inputMask="" attribute to field we will create a new,
more generic object. It would be represented in a .g?d file along the lines of
mask data
Valid type settings:
input : The mask applies during data input
display : The mask is applied prior to display
storage : The mask dictates how the data will be stored in the backend
validation : Used to validate information.
Samples
^SomeReg(e|x)
###-###-####
Valid style settings:
Styles are actually to be implemented as plugins. The generic mask object will not care about the
mask data passed into it. It will provide this data to the dynamically loaded plug in which will
do whatever it wishes with it. This way we could have a simple plugin that might want mask data
as
###-###-#####
AAAAA AAA AAAAAA
where # is for numbers and A is for text.
Or we could have more complex plugins like a regex plugin whos mask data contains a regular express.
Another possibility would be a python or trigger plugin that contains std python code.
By using plugins companies will be able to develop complex, custom plugins to validate their
data in any method they see fit