Can't pass concat challenge
See original GitHub issueChallenge concatenate-arrays-with-concat has an issue.
User Agent is: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36
.
Please describe how to reproduce this issue, and include links to screenshots if possible.
Same issue with filter and reverse challenge
var oldArray = [1,2,3];
var newArray = [];
var concatMe = [4,5,6];
// Only change code below this line.
newArray = oldArray.concat(concatMe);
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Concatenation Challenge Help (Example) - Treehouse
Concatenate the first name, last name and email address for all users. Alias it to to_field. ... Now I cannot pass the second...
Read more >Overcoming a concatenation challenge in Azure Synapse
Using PySpark in Azure Synapse Analytics and found that my regular way of concatenating two strings in T-SQL didn't work.
Read more >Best Way to Solve this Simple Concatenate Challenge?
It seems like loops would be the way to go. I set up a loop but can't get the dynamic variable to work....
Read more >How to Concatenate in Excel - GoSkills
There are four ways to concatenate in Excel (the CONCATENATE Excel function, ... range as the argument of the CONCAT function, which CONCATENATE...
Read more >How to concatenate strings using Python - KnowledgeHut
When you merge or combine two or more strings in Python, ... This is because strings are immutable i.e. they cannot be changed...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This has been fixed.
Seems to possibly be a similar bug as #10548, #10591, and #10589