[beta] Challenge mutate an array declared with const - Need Clearer instructions
See original GitHub issueChallenge mutate-an-array-declared-with-const has an issue.
User Agent is: Mozilla/5.0 (Windows NT 6.2; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.96 Safari/537.36
.
Please describe how to reproduce this issue, and include links to screenshots if possible.
This problem can be solved by changing the value of const s …In the description it tell that code below and code above this line …
const s = [ 2, 5, 7 ];
// change code below this line
// change code above this line
// Test your code
console.log(s);
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Mutate an Array Declared with const - Guide
Mutate an Array Declared with const Problem Explanation Reassign the values of the const variable s using various element assignment.
Read more >ES6 Lesson: Mutate an Array Declared with const - YouTube
Certification: JavaScript Algorithms and Data StructuresCourse: ES6Lesson: Mutate an Array Declared with constfreeCodeCamp tutorialIn this ...
Read more >How to Mutate an Array declared with const in JavaScript
By watching this video, you will learn how to modify an array previously declared with the const keyword. Thank you so much for...
Read more >NuSMV 2.6 User Manual
2.1.5 Array. Arrays are declared with a lower and upper bound for the index, and the type of the elements in the array....
Read more >Removing Effect Dependencies - React Docs
You might have noticed a pattern in your workflow: First, you change the code of your Effect or how your reactive values are...
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
@erictleung OK - no worries. Thanks for keeping me posted. This is a beta challenge so it’s OK if it takes another week or two for you to get to it.
@erictleung I agree,
Object.freeze()
should not be included in this challenge. However, it would be a great follow up to this challenge - immutable objects and arrays are really useful knowledge.If this challenge is created, should we perhaps open a separate issue for it?
@QuincyLarson How about something like this:
Object.freeze()
prevents any further changes to an object. This includes adding, removing or changing the values of properties and is useful to store constant data