Datepicker: allow the removal of masking via a new option

[awbuboltz]

Is your feature request related to a problem or use case? Please describe.
In the past (pre-4.51), we were able to use $elem.data('mask').destroy(); to effectively remove the masking from datepickers. That was an acceptable solution, but now that it's broken, we'd like to have something more permanently supported.

Describe the solution you'd like
A new datpicker option called something like { "useMask": false } that forgoes the addition of masking to the input field, allowing users to customize their own formatting.

Describe alternatives you've considered
One temporary solution I found with @EdwardCoyle was to add this.$elem.data('mask', null); after the destroy() call, which comes after initializing a datepicker. The reason this works is because

enterprise/src/components/datepicker/datepicker.js

Line 552 in 7be62f5

} else if (this.element.data('mask') === undefined) {

checks specifically for undefined, allowing null to pass though. For some reason, the entire mask is being set back up on blur, which seems wrong altogether, that gets called here:

enterprise/src/components/datepicker/datepicker.js

Line 287 in ed3870c

this.mask();

which is called by setCurrentCalendar() after the blur.

Additional context
Add any other context or screenshots about the feature request here.
And what application do you work on? [e.g. {Infor XYZ}]
Team: Lawson
Needed by: 4.61
@EdwardCoyle and I spent a good amount of time figuring this all out, so he's probably the guy for the job ;).

[tmcconechy]

Feel free @EdwardCoyle - I think just a setting to not invoke the mask seems entirely appropriate

[awbuboltz]

Note, this is team: lawson

[EdwardCoyle]

@tjamesallen15 two notes:

• We should forego the temporary solution described above because...
• this.mask(); probably shouldn't be called in setCurrentCalendar(), considering how often it can be called. You might also want to look into removing that as part of the PR for this issue, but it's unclear to me what the impact of that will be on any usage of Datepicker and Monthview components.

I think tasks for this issue are:

• add the setting useMask and default it to true
• tie the setting to invoking/destroying a mask component on the input
• create an example/test for explicitly-unmasked datepicker fields

[kaeleding]

Hi @tmcconechy, would like to ask an estimate for the 4.61 release date, since we are contemplating on applying the workaround on our end in line with our own release date.

It would be really helpful to us.

Thanks!

[tmcconechy]

Would be march 5-10 (start of march)

[tmcconechy]

Once completed will patch in 4.60.1

[jbrcna]

this issue is now resolved.
verified in https://main-enterprise.demo.design.infor.com/components/datepicker/test-disable-mask.html