This is not the best pratice. Because, every time you called the function task, actually you are creating the dic object. You should lift up the dic to function.

Wow...

For sure, it's not readeble.

Absolutely, this is not the best practice.

First, you don't need to use rest parameters. Because, we know that, Heron formula has a Exact 3 parameters(a, b, c). Not readeble.
Second. Dont use $ parameter unless you dont create the library or framework.
Third, ...$ this create already the variable. $ = [...$] that is not necessary.

Anyway, good solution but not the best practice.

You are damn right! This is not the best practice guy. Please, be responsible and dont vote for best practices.

cool, thanks for the link

I can't take credit for how cleverly ASCII was designed. Check out Tom Scott's take on character encodings here for some interesting history:

https://www.youtube.com/watch?v=MijmeoH9LT4

This is the best practice , not clever. If you are looking for the clever solution, look at that one - https://www.codewars.com/kata/reviews/59958a4aaca36cc0f1001e32/groups/5f5e0605e0be5a00011aaa89

I think that this is not best practice but removing space like this (charCodeAt % 32 === 0) is very clever...Good Job Man

One case where you can remove break is when you are returning a value in a case. So, if you "return" in case, it is totally ok.

Why?

This is not best practice!!! We should use regex for this kata.