If we migrate this to use parameters, we no longer need to have two separate datatypes for this functionality. The only difference I can recall between the two datatypes is that BirthDates are limited to being in the past.
We should consider renaming the input so it looks more like standard CSS input type names. E.g., consider following BEM.
It would probably be lower case. We want to keep PascalCase convention for the class name and we want it to be easily convertable from the Python class to the CSS input name. We also want to use AL prefixing in the name.
While I'm thinking of it - I think "split date" could be a good name. ALSplitDate for the class. Not sure what the datatype name can take as valid values - dashes, underscores, etc?
If we migrate this to use parameters, we no longer need to have two separate datatypes for this functionality. The only difference I can recall between the two datatypes is that BirthDates are limited to being in the past.
We should consider renaming the input so it looks more like standard CSS input type names. E.g., consider following BEM.
It would probably be lower case. We want to keep PascalCase convention for the class name and we want it to be easily convertable from the Python class to the CSS input name. We also want to use AL prefixing in the name.