Add is_scalar condition extends of is_string on some fiels about form

[terabytesoftw]

Good day. After last release null values are allowed and it's great. But i have some litle improvement. In my case phone numbers stored in DB on bigint column, so that failed with telephone::widget(). So maybe do that conditions in widget:

• Email/Url - is_string or null
• Number - is_numeric or null (as now)
• Date*** - maybe allow DateTime class?
• Others - is_scalar or null

Thanks

https://www.w3.org/TR/2012/WD-html-markup-20120329/input.tel.html#input.tel.attrs.value its string.

[Gerych1984]

Good day. After last release null values are allowed and it's great. But i have some litle improvement. In my case phone numbers stored in DB on bigint column, so that failed with telephone::widget(). So maybe do that conditions in widget:

• Email/Url - is_string or null
• Number - is_numeric or null (as now)
• Date*** - maybe allow DateTime class?
• Others - is_scalar or null

Thanks

https://www.w3.org/TR/2012/WD-html-markup-20120329/input.tel.html#input.tel.attrs.value its string.

Yes. If i set int phone as attribute (for example using Html helper), i will get string attribute value="71234567890" - it's html standart. But i can't on current widget. So maybe scalar values cast to string?

[terabytesoftw]

That sounds like a bad idea because we must cast scalar to string if you always want to get a string or type it string or not type it, scalar is not only numeric it is also boolean, the telephone widget is a string representation of a telephone number , because place it numeric, if it can contain [phone])