In this Regex Tutorial, you will learn how to validate the featured email address regular expression (regex) Regex Featured in This Tutorial: /^([a-z0-9_\.-]+)@([\da-z\.-]+)\.([a-z\.]{2,6})$/. The tutorial provides a comprehensive breakdown and explanation of each component within the regex, simplifying the validation process for easy understanding. Upon completing this tutorial, you will gain a deeper comprehension of how the regex functions to validate and confirm the entry of a valid email address.
GitHub Gist: Click Here
- Overview
- The Challenge
- Usage Information
- Installation Process
- Built With
- What I Learned
- Continued Development
- License
- Author
- Acknowledgments
In this challenge, you will utilize the knowledge gained from the tutorial and apply it to the creation of a comprehensive tutorial on email validation using regex. The following steps were taken to achieve this:
- Conducted a thorough literature review on the structure and format of email addresses.
- Identified the necessary components that need to be validated in an email address, utilizing information from peer-reviewed sources.
- Created a regex pattern that validates email addresses based on the identified components.
- Set up a GitHub Gist, following the instructions provided in the "Installation Process" section.
- In the newly created Gist, composed a brief explanation of the regex pattern created for email validation, describing each component and its purpose in the validation process. This explanation was informed by academic sources and tailored for novice coders and other academics.
- Shared the link to the Gist with others to discuss different approaches and understanding of the regex pattern.
The Sources Were Consulted:
- W3Resource. (n.d.). JavaScript: HTML Form - email validation. https://www.w3resource.com/javascript/form/email-validation.php
- University of Toronto. (n.d.). Teaching dossier. Centre for Teaching Support & Innovation. https://teaching.utoronto.ca/resources/teaching-dossier/
- Steipe, B. (n.d.). Regular expressions. University of Toronto: ABC: Always Be Coding. http://steipe.biochemistry.utoronto.ca/abc/index.php/Regular_Expressions
- University of Toronto Libraries. (n.d.). OpenRefine tutorial 3: Regular expressions (Regex) activity. https://mdl.library.utoronto.ca/technology/tutorials/openrefine-tutorial-3-regular-expressions-regex-activity
- University of Toronto. (n.d.). Oral presentations. Advice on Academic Writing. https://advice.writing.utoronto.ca/types-of-writing/oral-presentations/
- Harvard University. (2022). CS50's Web Programming with Python and JavaScript. https://cs50.harvard.edu/python/2022/weeks/7/
These sources provided valuable information on the construction and usage of regex patterns for email validation, as well as insights into the pedagogical aspects of teaching regex to new coders and other academics. This knowledge was incorporated into the creation of the comprehensive tutorial, which aimed to provide an accessible yet academically rigorous explanation of email validation using regex.
AS A web development student
I WANT a tutorial explaining a specific regex
SO THAT I can understand the search pattern the regex defines
GIVEN a regex tutorial
WHEN I open the tutorial
THEN I see a descriptive title and introductory paragraph explaining the purpose of the tutorial, a summary describing the regex featured in the tutorial, a table of contents linking to different sections that break down each component of the regex and explain what it does, and a section about the author with a link to the author’s GitHub profile
WHEN I click on the links in the table of contents
THEN I am taken to the corresponding sections of the tutorial
WHEN I read through each section of the tutorial
THEN I find a detailed explanation of what a specific component of the regex does
WHEN I reach the end of the tutorial
THEN I find a section about the author and a link to the author’s GitHub profile
- Access the deployed GitHub Gist link.
- Read through the introductory paragraph and summary.
- Navigate through the table of contents to explore the different sections of the tutorial.
- Read and understand each component of the regex pattern.
- Apply the knowledge gained from the tutorial in your own projects.
Deployed GitHub-Gist Link: Click Here
Set up a GitHub Gist:
- Sign in to your GitHub account or create one if you haven't already.
- Visit: https://gist.github.com/ to create a new Gist.
- In the "Gist description" field, enter a brief description of the challenge, such as "Email Regex Challenge".
- Add a new file to the Gist by clicking on "Add file" and give it a suitable name, like "email_regex_challenge.md".
- In your newly created Gist, write a brief explanation of the regex, describing each component and its purpose in the email validation process.
- Explain how the regex can be modified to accept new requirements, such as uppercase letters or additional special characters in the email address.
Share your Gist:
- Once you have completed the explanation and modifications to the regex, save your Gist by clicking on "Create public Gist" or "Create secret Gist" as per your preference.
- Share the link to your Gist with others to discuss different approaches and understanding of the regex.
By completing this challenge, you will not only have a better understanding of the email validation regex but also gain experience in setting up and sharing a GitHub Gist.
- Saiyan Pride
- GitHub Gist: How to Create a Gist?
- License Badge: Shields.io
- Visual Studio Code: Website
- Deployed my 1st GitHub Gist.
- Built knowledge and comprehension of regex patterns for email validation.
- Thorough breakdown on regex components.
- Effectively communicate the regex usage and validation techniques.
- Expanding regex patterns for additional validation use-cases.
- Creating tutorials for regex usage in other programming languages.
- Enhancing the tutorial with more examples and interactive elements.
- Sharing the tutorial with the developer community for feedback and improvements.
Copyright © 2023 Thomas Calle
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.Follow me on Github at Thomas Calle. Additional questions or concerns? feel free to contact me.
Until next, see you on the otherside!
© 2023 Thomas Calle. Confidential and Proprietary. All Rights Reserved.