Getting “compiled with warnings” for using regular expression
up vote
-2
down vote
favorite
iI'm getting compiled with warnings alert.
this is the message.
Compiled with warnings.
./src/components/register/register.js
Line 5: Unnecessary escape character: $ no-useless-escape
Line 5: Unnecessary escape character: ^ no-useless-escape
Line 5: Unnecessary escape character: * no-useless-escape
this is the code on line 5. I'm using it to check if a password contains 1 upper case, 1 lower case, 1 number, 1 special character and if its longer than 8 characters.
const passwordRegex = RegExp(/^(?=.*[a-z])(?=.*[A-Z])(?=.*[0-9])(?=.*[!@#$%^&*])(?=.{8,})/);
I'm wondering why am I getting this alert? and how do I make it go away?
javascript reactjs
asked Nov 10 at 18:17
ylimes
2216
add a comment |
up vote
-2
down vote
favorite
iI'm getting compiled with warnings alert.
this is the message.
Compiled with warnings.
./src/components/register/register.js
Line 5: Unnecessary escape character: $ no-useless-escape
Line 5: Unnecessary escape character: ^ no-useless-escape
Line 5: Unnecessary escape character: * no-useless-escape
this is the code on line 5. I'm using it to check if a password contains 1 upper case, 1 lower case, 1 number, 1 special character and if its longer than 8 characters.
const passwordRegex = RegExp(/^(?=.*[a-z])(?=.*[A-Z])(?=.*[0-9])(?=.*[!@#$%^&*])(?=.{8,})/);
I'm wondering why am I getting this alert? and how do I make it go away?
javascript reactjs
asked Nov 10 at 18:17
ylimes
2216
1
Well, the warnings are telling you what's wrong. Why not just heed what they say? The escapes they mention are unnecessary (because they occur inside a range).
– Utkanos
Nov 10 at 18:29
because I'm new to this. the reason why I asked...
– ylimes
Nov 10 at 18:33
I can appreciate that - we're all new to things are some time. But in your case the warnings are telling you exactly what's wrong. Duskwuff's answer expounds on why these characters don't need escaping.
– Utkanos
Nov 10 at 18:33
add a comment |
up vote
-2
down vote
favorite
up vote
-2
down vote
favorite
iI'm getting compiled with warnings alert.
this is the message.
Compiled with warnings.
./src/components/register/register.js
Line 5: Unnecessary escape character: $ no-useless-escape
Line 5: Unnecessary escape character: ^ no-useless-escape
Line 5: Unnecessary escape character: * no-useless-escape
this is the code on line 5. I'm using it to check if a password contains 1 upper case, 1 lower case, 1 number, 1 special character and if its longer than 8 characters.
const passwordRegex = RegExp(/^(?=.*[a-z])(?=.*[A-Z])(?=.*[0-9])(?=.*[!@#$%^&*])(?=.{8,})/);
I'm wondering why am I getting this alert? and how do I make it go away?
javascript reactjs
asked Nov 10 at 18:17
ylimes
2216
iI'm getting compiled with warnings alert.
this is the message.
Compiled with warnings.
./src/components/register/register.js
Line 5: Unnecessary escape character: $ no-useless-escape
Line 5: Unnecessary escape character: ^ no-useless-escape
Line 5: Unnecessary escape character: * no-useless-escape
this is the code on line 5. I'm using it to check if a password contains 1 upper case, 1 lower case, 1 number, 1 special character and if its longer than 8 characters.
const passwordRegex = RegExp(/^(?=.*[a-z])(?=.*[A-Z])(?=.*[0-9])(?=.*[!@#$%^&*])(?=.{8,})/);
I'm wondering why am I getting this alert? and how do I make it go away?
javascript reactjs
javascript reactjs
asked Nov 10 at 18:17
ylimes
2216
asked Nov 10 at 18:17
ylimes
2216
edited Nov 10 at 18:25
asked Nov 10 at 18:17
ylimes
2216
asked Nov 10 at 18:17
ylimes
2216
asked Nov 10 at 18:17
ylimes
2216
2216
1
Well, the warnings are telling you what's wrong. Why not just heed what they say? The escapes they mention are unnecessary (because they occur inside a range).
– Utkanos
Nov 10 at 18:29
because I'm new to this. the reason why I asked...
– ylimes
Nov 10 at 18:33
I can appreciate that - we're all new to things are some time. But in your case the warnings are telling you exactly what's wrong. Duskwuff's answer expounds on why these characters don't need escaping.
– Utkanos
Nov 10 at 18:33
add a comment |
1
Well, the warnings are telling you what's wrong. Why not just heed what they say? The escapes they mention are unnecessary (because they occur inside a range).
– Utkanos
Nov 10 at 18:29
because I'm new to this. the reason why I asked...
– ylimes
Nov 10 at 18:33
I can appreciate that - we're all new to things are some time. But in your case the warnings are telling you exactly what's wrong. Duskwuff's answer expounds on why these characters don't need escaping.
– Utkanos
Nov 10 at 18:33
1
1
Well, the warnings are telling you what's wrong. Why not just heed what they say? The escapes they mention are unnecessary (because they occur inside a range).
– Utkanos
Nov 10 at 18:29
Well, the warnings are telling you what's wrong. Why not just heed what they say? The escapes they mention are unnecessary (because they occur inside a range).
– Utkanos
Nov 10 at 18:29
because I'm new to this. the reason why I asked...
– ylimes
Nov 10 at 18:33
because I'm new to this. the reason why I asked...
– ylimes
Nov 10 at 18:33
I can appreciate that - we're all new to things are some time. But in your case the warnings are telling you exactly what's wrong. Duskwuff's answer expounds on why these characters don't need escaping.
– Utkanos
Nov 10 at 18:33
I can appreciate that - we're all new to things are some time. But in your case the warnings are telling you exactly what's wrong. Duskwuff's answer expounds on why these characters don't need escaping.
– Utkanos
Nov 10 at 18:33
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
The warning is pointing out -- correctly -- that the characters $, ^, and * do not need to be escaped in the character class [!@#$%^&*]. The only characters with special meanings in this context are [, ], -, and .
answered Nov 10 at 18:30
duskwuff
144k19174225
thank you for explaining
– ylimes
Nov 10 at 18:35
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
The warning is pointing out -- correctly -- that the characters $, ^, and * do not need to be escaped in the character class [!@#$%^&*]. The only characters with special meanings in this context are [, ], -, and .
answered Nov 10 at 18:30
duskwuff
144k19174225
thank you for explaining
– ylimes
Nov 10 at 18:35
add a comment |
up vote
1
down vote
The warning is pointing out -- correctly -- that the characters $, ^, and * do not need to be escaped in the character class [!@#$%^&*]. The only characters with special meanings in this context are [, ], -, and .
answered Nov 10 at 18:30
duskwuff
144k19174225
thank you for explaining
– ylimes
Nov 10 at 18:35
add a comment |
up vote
1
down vote
up vote
1
down vote
The warning is pointing out -- correctly -- that the characters $, ^, and * do not need to be escaped in the character class [!@#$%^&*]. The only characters with special meanings in this context are [, ], -, and .
answered Nov 10 at 18:30
duskwuff
144k19174225
The warning is pointing out -- correctly -- that the characters $, ^, and * do not need to be escaped in the character class [!@#$%^&*]. The only characters with special meanings in this context are [, ], -, and .
answered Nov 10 at 18:30
duskwuff
144k19174225
answered Nov 10 at 18:30
duskwuff
144k19174225
answered Nov 10 at 18:30
duskwuff
144k19174225
answered Nov 10 at 18:30
duskwuff
144k19174225
144k19174225
thank you for explaining
– ylimes
Nov 10 at 18:35
add a comment |
thank you for explaining
– ylimes
Nov 10 at 18:35
thank you for explaining
– ylimes
Nov 10 at 18:35
thank you for explaining
– ylimes
Nov 10 at 18:35
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53242012%2fgetting-compiled-with-warnings-for-using-regular-expression%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Well, the warnings are telling you what's wrong. Why not just heed what they say? The escapes they mention are unnecessary (because they occur inside a range).
– Utkanos
Nov 10 at 18:29
because I'm new to this. the reason why I asked...
– ylimes
Nov 10 at 18:33
I can appreciate that - we're all new to things are some time. But in your case the warnings are telling you exactly what's wrong. Duskwuff's answer expounds on why these characters don't need escaping.
– Utkanos
Nov 10 at 18:33