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
Challenge [Access MultiDimensional Arrays With Indexes] Solving Bug #10126
Comments
@Pablo152 thanks for the issue. You are correct, this is a bug of sorts. Mmm to catch this kind of code, it might be difficult. We could add in two tests:
cc/ @FreeCodeCamp/issue-moderators |
@erictleung One or both of those tests could be combined with the |
@erictleung I agree with @BKinahan - as we add more tests to address various corner cases that come up, we tuck these behind as few tests as possible to avoid intimidating campers with a wall of tests. |
@QuincyLarson @BKinahan sounds good! I think we can just add to the |
@erictleung I think we need both your test above and the aforementioned regex for /myData = \d/ because I can set myData = [2][2]; and still run the nefarious code |
@dhcodes sounds reasonable. As @QuincyLarson has mentioned, try to minimize the number of tests we need to add, if any. So for regex looking for |
@dhcodes said he wasn't working on this, so I grabbed it up 😄 |
While the 4+4 solution does solve the challenge, the correct way to solve based on the directions,"using bracket notation select an element from myArray such that myData is equal to 8", would be: // Setup // Only change code below this line. |
myArray[2][1]; |
nice topic that i learn, |
Challenge Access MultiDimensional Arrays With Indexes
has an issue.
User Agent is:
Mozilla/5.0 (Windows NT 10.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.82 Safari/537.36
.Please describe how to reproduce this issue, and include links to screenshots if possible.
I just used myData = 4 + 4 to get myData = 8 and i solved the challenge that way, if i'm not wrong that's a bug soo...
My code:
The text was updated successfully, but these errors were encountered: