-
-
Notifications
You must be signed in to change notification settings - Fork 777
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change input validation settings on WINS form to prevent invalid URL entries #4595
Comments
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
Hi @brianf4, thank you for taking up this issue! Hfla appreciates you :) Do let fellow developers know about your:- You're awesome! P.S. - You may not take up another issue until this issue gets merged (or closed). Thanks again :) |
Availability: Sunday - Friday 10 am - 8 pm |
Thanks @brianf4 - This looks good to me but I'd like to give the merge team a few days to test the form as well. |
@brianf4 @roslynwythe I tried different variations and tried to think of an exception to trip up the regex. So far everything looks good to me. |
Thank you @brianf4 for great work on this issue. The regular expressions you created will help to ensure that our Wins form recieves valid URLs. |
Prerequisite
Overview
As developers we need to update input validation settings on the LinkedIn URL and GitHub URL fields of the "Share your WINS" form, so that invalid URLs are not accepted.
Action Items
http://
,https://
, or it could be blank.www.github.com/
orgithub.com/
www.linkedIn.com/in/
orlinkedIn.com/in/
/
Merge Team/Dev Leads
Resources/Instructions
The text was updated successfully, but these errors were encountered: