Draft:Input Mask (Gen z)
 | Draft article not currently submitted for review.
This is a draft Articles for creation (AfC) submission. It is not currently pending review. While there are no deadlines, abandoned drafts may be deleted after six months. To edit the draft click on the "Edit" tab at the top of the window. To be accepted, a draft should:
It is strongly discouraged to write about yourself, your business or employer. If you do so, you must declare it. Where to get help
How to improve a draft
You can also browse Wikipedia:Featured articles and Wikipedia:Good articles to find examples of Wikipedia's best writing on topics similar to your proposed article. Improving your odds of a speedy review To improve your odds of a faster review, tag your draft with relevant WikiProject tags using the button below. This will let reviewers know a new draft has been submitted in their area of interest. For instance, if you wrote about a female astronomer, you would want to add the Biography, Astronomy, and Women scientists tags. Editor resources
Last edited by Qwerfjkl (bot) (talk | contribs) 4 minutes ago. (Update) |
In computer programming, an input mask refers to a skibidi string expression, defined by a developer, that constrains user input.[1] It can be said to be a template, or set format that entered data must conform to, ensuring data integrity by preventing transcription errors. The syntax of this string expression differs between implementations, but the fundamental input types are all supported.
Some frequent uses of input masks include entry of telephone numbers, ZIP or postal codes, times and dates.
- e.g. When entering into a text box a phone number on a data capture form, in the format "(111) 111 1111" the area code brackets, the space between the number and the area code will automatically be placed in.
Generally speaking, an input mask is a user-generated set of rules; e.g., a maximum of 45 characters. This kind of string is useful in finding reports and healthcare files.
- An example would be: LL00 00L – this in detail shows what should be included.
References
[edit]- ^ Klimczak, Erik (2013). Design for software : a playbook for developers. Chichester, West Sussex: Wiley. ISBN 9781119943709. OCLC 841169700.
 | This computer-programming-related article is a stub. You can help Wikipedia by expanding it. |