DEV Community

Cover image for 8 Best JavaScript One-Liners

8 Best JavaScript One-Liners

Shivam Singh on September 15, 2023

Hey everyone! If you're new to coding, you're probably excited but maybe a little overwhelmed, right? Don't sweat it! 😅 Today, we're going to look ...
Collapse
 
jonrandy profile image
Jon Randy 🎖️ • Edited

3) can be shorter:

const sortBy = (arr, key) => arr.sort((a, b) => a[key] > b[key] || -1)
Enter fullscreen mode Exit fullscreen mode

5) You have not shown how to use the function, and it will only delay the execution of code chained with the Promise. Statements immediately after will proceed as normal with no delay.

6) Your input is missing the key.

7) Your input shown is wrong, and this can also be shorter - using the built-in method designed for the purpose:

const insert = (arr, index, newItem, a=[...arr]) => (a.splice(index, 0, newItem), a)
Enter fullscreen mode Exit fullscreen mode

8) Will not function correctly as it will never return #ffffff, and also many other colours as you are not padding the string with leading zeroes. A correct version:

const randomColor = "#" + (~~(Math.random() * 8**8)).toString(16).padStart(6,0)
Enter fullscreen mode Exit fullscreen mode
Collapse
 
skyjur profile image
Ski • Edited

#3: when sorting numbers just use subtraction for numbers just do a - b for ascending order

arr.sort((a, b) => a[key] - b[key])
Enter fullscreen mode Exit fullscreen mode

and for strings use a.localeCompare(b)

Collapse
 
shivams1007 profile image
Shivam Singh

Yes, this is also correct!

Collapse
 
shivams1007 profile image
Shivam Singh

1. The chill Function

You're correct; my initial example did not show how to actually use the function in a meaningful way. It's a Promise-based function, so you'd typically use it with async/await or .then() to actually cause a delay in the code's execution. Here's how you could use it:

(async () => {
  console.log("Before waiting");
  await chill(2000);
  console.log("After waiting for 2 seconds");
})();
Enter fullscreen mode Exit fullscreen mode

2. The sortBy Function

You bring up a good point. The function could indeed be simplified to:

const sortBy = (arr, key) => arr.sort((a, b) => a[key] > b[key] ? 1 : -1);
Enter fullscreen mode Exit fullscreen mode

This approach assumes that a[key] and b[key] will never be equal if sorting is based on unique identifiers, which might be okay for some cases but not all.

3. The pluck Function

You're right; the input was incomplete without specifying the key. A more full example could be:

const pluck = (arr, key) => arr.map(obj => obj[key]);
console.log(pluck([{x: 1}, {x: 2}], 'x')); // Output: [1, 2]
Enter fullscreen mode Exit fullscreen mode

4. The insert Function

Your point is valid; the input example could have been more complete. Also, your shorter version using splice is more concise. However, one benefit of the original slice approach is that it does not mutate the original array.

const insert = (arr, index, newItem, a=[...arr]) => (a.splice(index, 0, newItem),a);
Enter fullscreen mode Exit fullscreen mode

5. The randomColor Function

You are correct again; the original version can indeed skip some colors and never reach #FFFFFF. Your version with padding zeros is more accurate in generating the full spectrum of colors:

const randomColor = "#" + (~~(Math.random() * 8**8)).toString(16).padStart(6,0);
Enter fullscreen mode Exit fullscreen mode

Thank you for pointing out these details; your observations are insightful and enhance the accuracy and efficiency of the examples.
I will update it according to it!

Collapse
 
jonrandy profile image
Jon Randy 🎖️ • Edited

Try the shorter sortBy with repeated identifiers. Works just fine. If the two identifiers are equal it makes no difference what order they are sorted in.

My splice example doesn't mutate the original array.

Thread Thread
 
jonrandy profile image
Jon Randy 🎖️

Might want to fix the glaring typo in the header image too! 😉

Thread Thread
 
shivams1007 profile image
Shivam Singh

@jonrandy which one?

Thread Thread
 
jonrandy profile image
Jon Randy 🎖️

"8 One-Linear You Will Love"

Thread Thread
 
shivams1007 profile image
Shivam Singh • Edited

ohh yes you are correct! 😊
I am open for any other suggestions

Collapse
 
shivams1007 profile image
Shivam Singh

1. The sortBy Function with Repeated Identifiers

You're right that if two elements have the same identifier, the order doesn't matter for those particular elements. In many sorting algorithms, including JavaScript's native .sort(), elements that compare as equal remain in their original order (stable sort). So, your simplified version is equally effective:

const sortBy = (arr, key) => arr.sort((a, b) => a[key] > b[key] ? 1 : -1);
Enter fullscreen mode Exit fullscreen mode

This will work just fine even with repeated identifiers.

2. The splice Example and Array Mutation

I apologize for the misunderstanding. You're correct; your example using splice actually doesn't mutate the original array because you made a shallow copy (a=[...arr]) before applying the splice.

Here's the function for clarity:

const insert = (arr, index, newItem, a=[...arr]) => (a.splice(index, 0, newItem),a);
Enter fullscreen mode Exit fullscreen mode

In this function, a=[...arr] creates a new array that is a copy of the original arr. Then, splice is called on this new array (a), so the original arr remains unchanged. Therefore, it is a non-mutating operation on the original array.

Thank you for your keen observations; they serve to improve the quality and accuracy of the discussion.

Collapse
 
dannyengelman profile image
Danny Engelman

My favorite oneliner when building Web Components, or any DOM is:

const element=(t,p={})=>Object.assign(document.createElement(t), p);
Enter fullscreen mode Exit fullscreen mode

Click the Result tab:

Collapse
 
shivams1007 profile image
Shivam Singh

Great!

Collapse
 
skyjur profile image
Ski • Edited

Please never do #4: comparing using JSON.stringify(a) == JSON.stringify(b). It's very poor practice: it doesn't guarantee correctness - in some cases it can give false positive as well as false negative (for instance objects equal but key order is not JSON stringify will produce different output) - as some objects might not get stringified at all, and some values can even result into json.stringify throwing an error.

If you have class objects, then good idea is to implement equal() method on your object and compare a.equal(b). For generic object use recursive algorithm.

But more importantly consider why do you need deep equality check in first place - as it can be computationally intensive. Likely there should be ways to avoid it in first place.

Collapse
 
shivams1007 profile image
Shivam Singh

Yes it doesn't give a correct solution for every scenario

Collapse
 
webjose profile image
José Pablo Ramírez Vargas

While I'm not saying that all of these suffer from it, this is the kind of programming that leads to performance hell. People get so used to shorthand versions of things (mostly loop-based), that end up enumerating collections an enormously unnecessary amount of times.

This is also found in .Net and the LINQ advocates.

Bottom line: Shorter is more commonly worse than you think. Analyze your algorithms thoroughly.

Collapse
 
shivams1007 profile image
Shivam Singh • Edited

It's not totally correct. It depends

Collapse
 
lucasm4sco profile image
Lucas

Great, I think it would be useful to also comment that it can happen that objects with the same values ​​still return false when compared with stringify method due to the order of their properties

Collapse
 
shivams1007 profile image
Shivam Singh

yes correct!

Collapse
 
jamesgj5 profile image
James Graça-Jones

Thanks for the article, I definitely learnt a lot from this! I slightly worry that some of the wording in Point 4 distracts the reader from realising that just because two arrays have the same values doesn't mean they actually are the same. They aren't the same object, for example, they just have the same values in them. Fun article though :)

Collapse
 
shivams1007 profile image
Shivam Singh

thanks

Collapse
 
arielmejiadev profile image
Ariel Mejia

Hi @shivamblog If it makes sense to you I would add a one-liner to shuffle and pick items from an array:

const randomizeArray = () => [...array].sort(() => 0.5 - Math.random()).slice(0, items);
Enter fullscreen mode Exit fullscreen mode
Collapse
 
shivams1007 profile image
Shivam Singh

what is items here?

Collapse
 
arielmejiadev profile image
Ariel Mejia

@shivamblog Sorry items could be the number of items so you can shuffle and also get only some of them:

and the array should be the array to shuffle and slice it.

const randomizeArray = () => [...array].sort(() => 0.5 - Math.random()).slice(0, numberOfItems);
Enter fullscreen mode Exit fullscreen mode
Thread Thread
 
shivams1007 profile image
Shivam Singh

Then it is correct!

Collapse
 
tobiasss97 profile image
Tobiasss97

Great post

Collapse
 
shivams1007 profile image
Shivam Singh

thanks!