Quiz time! What's wrong with our customMax function? How do we fix it?
Hint: check out the second image, where we show "customMax" in use
For further actions, you may consider blocking this person and/or reporting abuse
DEV Community
Need a better mental model for async/await?
Check out this classic DEV post on the subject.
⭐️🎀 JavaScript Visualized: Promises & Async/Await
Read next
Puzzle Classic "Baba is You" recreated in JavaScript - Behind the Code
Michael Z -
Ever wonder why React's setState doesn't update immediately?
vatana7 -
The new React docs
M. Akbar Nugroho -
Creating Countdown Timer with Vuejs Composables
Andrew Zachary -
Latest comments (1)
All non-primitives are passed by reference in es, so we're effectively passing the same array to the sort function. That's why the array is sorted afterwards. The solution would be to clone the array to a new variable before sorting it (i.e. by using the spread operator
const larr = [...arr])