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







share|improve this question




















  • 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

















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







share|improve this question




















  • 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















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







share|improve this question















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






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 10 at 18:25

























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
















  • 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














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 .






share|improve this answer





















  • thank you for explaining
    – ylimes
    Nov 10 at 18:35











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














 

draft saved


draft discarded


















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

























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 .






share|improve this answer





















  • thank you for explaining
    – ylimes
    Nov 10 at 18:35















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 .






share|improve this answer





















  • thank you for explaining
    – ylimes
    Nov 10 at 18:35













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 .






share|improve this answer












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 .







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 10 at 18:30









duskwuff

144k19174225




144k19174225












  • 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




thank you for explaining
– ylimes
Nov 10 at 18:35


















 

draft saved


draft discarded



















































 


draft saved


draft discarded














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





















































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







-

Popular posts from this blog

Florida Star v. B. J. F.

Image
Florida Star v. B. J. F. From Wikipedia, the free encyclopedia Jump to navigation Jump to search United States Supreme Court case Florida Star v. B. J. F. Supreme Court of the United States Argued March 21, 1989 Decided June 21, 1989 Full case name The Florida Star v. B. J. F. Citations 491 U.S. 524 ( more ) 109 S. Ct. 2603; 105 L. Ed. 2d 443; 1989 U.S. LEXIS 3120; 57 U.S.L.W. 4816; 16 Media L. Rep. 1801 Prior history The Florida Star v. B.J.F., 530 So.2d 286 (1988) Supreme Court of Florida; Florida Star v. B.J.F., 499 So.2d 883 (1986) Fla. Dist. Court of Appeals Holding Florida Stat. § 794.03 is unconstitutional to the extent it makes the truthful reporting of information that was a matter of public record unlawful, as it violates the First Amendment. Court membership Chief Justice William Rehnquist Associate Justices William J. Brennan Jr.  · Byron White Thurgood Marshall  · Harry Blac
Read more

Error while running script in elastic search , gateway timeout

Image
0 while running script in elastic search, I got 504 Gateway timeout error. { "query": { "bool": { "filter": { "script": { "script": " doc['creted_date'].date.getMonthOfYear() == 12 " } } } }, "aggs": { "test": { "date_histogram": { "field": "creted_date", "interval": "month", "format": "MMM" }, "aggs": { "cost": { "sum": { "field": "cost" } } }
Read more

Adding quotations to stringified JSON object values

Image
0 My stringified object data doesn't include quotation marks around object values, which errors when attempting JSON.parse() : '{ "affiliation": CORPORATE, "userId": 75c35d1c-5d12-4485-8fa8-b2f1551a3e6e }' I need the string to be: '{ "affiliation": "CORPORATE", "userId": "75c35d1c-5d12-4485-8fa8-b2f1551a3e6e" }' I'm using this regex to add quotes to the object keys: var newStr = str.replace(/(['"])?([a-z0-9A-Z_]+)(['"])?:/g, '"$2": '); For instance: '{ affiliation: CORPORATE }' to '{ "affiliation": CORPORATE }' There are only string values in my data, so I don't need to check value types. How can I alter my regex expression to add quotations to
Read more