Freecodecamp: [beta] bug in "Quoting String with Single Quotes" challenge

[strongdan]

Challenge quoting-strings-with-single-quotes has an issue.
User Agent is: Mozilla/5.0 (X11; CrOS x86_64 8872.76.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.105 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.

var myStr = '<a href="http://www.example.com" target="_blank">Link</a>';

[tommygebru]

Im seeing it differently the first test passes, but the second test fails....
It does not pass this challenge:

-You should have two single quotes'and four double quotes"

var myStr = '<a href="http://www.example.com" target="_blank">Link</a>';

MBP using Google Chrome.

[strongdan]

Weird. I was using Chrome on a Chromebook.

Is it better for me to simply state the nature of the bug or should I attempt to fix the testing files and create a pull request?

[tommygebru]

I believe its good to share as an issue first and get feedback...
also its pretty important to consistently provide screenshots also its easier to explain this way!

[strongdan]

Okay, I will do that in the future. I'm very new to all of this. I re-ran this challenge and got the same result - failed second test but passed first.

[tommygebru]

yeah - its an issue for sure

[marvelousdesign]

I'm having this error too and mines doesn't see the back slashes been removed.

[no-stack-dub-sack]

@strongdan Thanks for reporting this issue. I've also been able to confirm this. Funny because the same challenge works in production. I have a hunch as to what the issue is though...

[no-stack-dub-sack]

Ok, so the issue with this is similar to what we're seeing in this issue... what's happening is that there's a multi-line comment that is invisible to users, and the below test is counting all the quotes that are found in the code variable, which includes the invisible multi-line comment. The comment includes 'use strict' which is throwing off the count.

assert(code.match(/\"/g).length === 4 && code.match(/'/g).length === 2, 'message: You should have two single quotes <code>&#39;</code> and four double quotes <code>&quot;</code>');

So I can make a quick PR to fix this issue as I already fixed locally when I was playing around to confirm that that's what the issue was

[RandellDawson]

I am having the same problem with the correct solution, but if I exit the challenge and re-enter using the Map and submit, it passes the tests fine.

[no-stack-dub-sack]

@rmdawson71 this pull request should fix this issue! It should be updated and working on the beta site within the next couple of days!

[RandellDawson]

Hi Peter,

How would I have known not to comment or create a new “ticket” for a bug that has a fix but has not been implemented. It seems you all maybe getting numerous repeat notifications about bugs that already have a fix for them. I am not sure If it was this challenge or another one, I first checked github for previously reported issues on the challenge. If it still showed “Open” and someone already commented with same problem I saw, I did nothing. However, if there was not report of my issue or there was but the status was “Closed”, I made another comment on it and posted my screenshot and comments.

Am I approaching this correctly?

Randell Dawson

One Path Technologies

Phone: [phone]

Email: [email protected]

From: Peter Weinberg [mailto:[email protected]]
Sent: Monday, January 30, 2017 8:49 PM
To: freeCodeCamp/freeCodeCamp [e-mail]
Cc: Randell Dawson [e-mail]; Mention [e-mail]
Subject: Re: [freeCodeCamp/freeCodeCamp] [beta] bug in "Quoting String with Single Quotes" challenge (#12865)

@rmdawson71 https://github.com/rmdawson71 this pull request should fix this issue! It should be updated and working on the beta site within the next couple of days!

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/freeCodeCamp/freeCodeCamp/issues/12865#issuecomment-276274291 , or mute the thread https://github.com/notifications/unsubscribe-auth/AFESveIR1eMvhw683sCyEucqw-ZvBpbpks5rXr1XgaJpZM4LuT5t . https://github.com/notifications/beacon/AFESvd-jrIoscR7wPZgShLYEmq6eFjNWks5rXr1XgaJpZM4LuT5t.gif

[RandellDawson]

Not sure if you got my other message, but why is it marked close if the fix has not been put in place?

[Greenheart]

@rmdawson71 Thanks reporting this! You've done everything correctly - this problem might still exist for a few days since it usually takes some time before a submitted fix is live on the site.

If you still experience this issue in a few days, even after a hard refresh (CTRL+SHIFT+R) and press the "Reset" button in the instructions panel (to make sure you're using the latest challenge data), then please comment here.

Otherwise, thanks for contributing to freeCodeCamp and happy bug hunting! :blush:

[cecilebertin]

This challenge is still bugged on Safari on the beta. I had the same issue as @marvellousdesign. I had to do a couple of hard refresh before it worked.

[gulptech]

Still a problem. Refreshing page fixes the problem.

[Leonardscripts]

freecodecamp was great before all this beta nonsense came about. its been about a month now since released an yet you think all these basics would have been fixed. i am all for knew stuff added to the knew diet of code on the camps site but they really screwed up a lot of stuff that was working just fine an teaching people a solid way to learn an implement knew information to there brains. i noticed they brought back the hint button which i rarely ever used but on occasion had to. but yet that doesn't work either.