Just in case:

VM1509:1 Uncaught EvalError: Refused to evaluate a string as JavaScript because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive: "script-src chrome://resources chrome://webui-test 'self'".

true

Of course, "brevity is the soul of wit" ..... But I would like to emphasize 3 points here:

1. Safety: Using eval can be dangerous if the input is not fully controlled. This can lead to the execution of unwanted or malicious code, which can be a security risk.

2. Performance: eval can be slower than other code execution methods because it requires interpreting the string as code.

3. Debugging and readability: Code that uses eval can be more difficult to debug and maintain. This can make the code less predictable and harder to understand.

I'm not judging, just sharing my opinion. Alternatively, you can use switch-case or map.

???

I want to reach this level of skill.

what is this sorcery? was your father a mac or a man?

I agree

it looks good and cool because it only uses one line, but you also need to pay attention to security, not just one line,
for example if the user inputs something that is not appropriate such as ("I'm a bad hexker", 2,10)
in the real world it will definitely be detrimental in the future,|

This is not judging but just giving advice

Nice Security ...

Not best practice even in the slightest. Passing unknown variables into a method that can open your codebase to injection attacks, good luck in real job.

Who the fk are those 541 people who voted for "Best Practices"?

Incredible