Change:
Describe your problem and how to reproduce it: The test "Call functionWithArgs with two numbers after you define it." doesn't passes if the function call doesn't end with semi column. As in js semi columns are not required it should pass even if user doesn't add semi column Add a Link to the page with the problem: Tell us about your browser and operating system: Browser Name: Chrome Browser Version: latest Operating System: windows 10 If possible, add a screenshot here (you can drag and drop, png, jpg, gif, etc. in this box): ! !
There has been an on and off discussion for a while about whether to enforce the use of end-of-line statement semi-colons. W FYI - This debate about semi-colons is not new to FCC. This is a debate that has been going on for a long time. See the following link how not using semi-colons could cause unexpected errors. This debate is similar to whether or not you should require { and } if there is only one statement in the code block. For example: is the same as: but FCC's current linter settings expect the { and } to be used. Both are valid JavaScript, but it is thought using { and } makes it clear especially when you have a line after like below: OR Both of the above accomplish the same thing, but reading the code could get confusing especially if indentation of the second line was accidentally written as: Someone coming from Python might thing the second line is far of the if statement block when it is not. As far as the semi-colon debate goes, I don't care which way it is done, just as long as it is consistent throughout the curriculum. Currently, there are challenges which do not require the semi-colon and some which do (which you have observed).
Well as these tutorials requires user to type regular JavaScript code. It would make sense to treat the code same as regular javascripts treats it's. If the function returns correct result. Code should pass the test.
Are you referring to semi-colons or the curly brackets now?
I have eleborate my answer. And I am taking about semicolons.
I have asked those in charge to make a final decision about this issue. Once I get some feedback, I will let you know the verdict. This decision will affect many challenges.
Hi, By any chance have they took a decision about this issue? I can confirm that this is still an issue after 3 months. When you get used to code using the standardJS style(), for example, it's not immediately obvious that the "Call function" test is not passing due to a missing semicolon. I don't mind whether you decide to keep the semicolons or let them be optional, as it comes to coding style. But a failing test should indicate the real problem, and I feel that failing a test named "Call function after you define it" when you actually called your function properly, can be confusing to new developers. Cheers, Mike
Yes, would you be interested in making the semi-colon optional for this challenge to pass the tests?
sure! Just let me get familiar with the code base and as soon as I have a better grasp, I will send the pr's for this challenge and the next one (that is under the same situation).
Any progress on this I agree that the semi-colons should be optional - If a camper is failing a challenge with valid javascript, that seems like a problem that might confuse them.

Discussion:
- text: <code>functionWithArgs(7,9)</code> should output <code>16</code> testString: if(typeof functionWithArgs === "function") { capture(); functionWithArgs(7,9); uncapture(); } assert(logOutput == 16); - text: Call <code>functionWithArgs</code> with two numbers after you define it. <del> testString: assert(/^s*functionWithArgss*(s*d+s*,s*d+s*)s*;/m.test(code)); </del> <ins> testString: assert(/^s*functionWithArgss*(s*d+s*,s*d+s*)s*/m.test(code)); </ins> ```