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
Need a better mental model for async/await?
Check out this classic DEV post on the subject.
Michael Z -
M. Akbar Nugroho -
Andrew Zachary -
Once suspended, vuetraining will not be able to comment or publish posts until their suspension is removed.
Once unsuspended, vuetraining will be able to comment and publish posts again.
Once unpublished, all posts by vuetraining will become hidden and only accessible to themselves.
If vuetraining is not suspended, they can still re-publish their posts from their dashboard.
Once unpublished, this post will become invisible to the public and only accessible to VueTraining.net.
They can still re-publish the post if they are not suspended.
Thanks for keeping DEV Community safe. Here is what you can do to flag vuetraining:
Unflagging vuetraining will restore default visibility to their posts.
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])