Java script

[mirkashi]

Select Topic Area

General

Body

If anyone knows about JavaScript, please DM me. I wanted to ask something and discuss some issues related to JavaScript conversion operations. ↩️

[shinybrightstar]

Welcome to the GitHub Community, @mirkashi, we're happy you're here! You are more likely to get a useful response if you are posting your question(s) in the applicable category. Check out this Guide on how to post in the right category. It'll ensure your questions and discussions reach the right people faster!

This particular discussion belongs in the Programming Help category, I've gone ahead and moved it for you. Good luck!

[mirkashi]

thank i understand

[jihanurrahman33]

Hi @mirkashi,

Feel free to share the specific conversion issue you’re running into here in the thread instead of DM. That way more people in the community can see it, suggest solutions, and others who run into the same problem later can benefit too.

What kind of conversion are you working on — e.g., string ↔ number, JSON parsing, or type coercion?

[mirkashi]

I'm dealing with JavaScript's type coercion issue. Specifically, when I perform an operation like adding a number to a string, JavaScript automatically converts the number into a string and concatenates them instead of doing arithmetic.

For example:
let result = 2 + "2";
console.log(result); // "22" (string), not 4.

So my question is mainly about why this happens and how to handle such conversions properly.

what’s the best practice to avoid these unexpected type coercions — should I rely on strict equality (===), manual type casting (Number(), String()), or is there another recommended approach?

[jihanurrahman33]

Hi @mirkashi,

Great question — you’ve run into one of the classic “gotchas” in JavaScript.

Why it happens

When using the + operator, JavaScript will favor string concatenation if either operand is a string:

let result = 2 + "2";
console.log(result); // "22" (string)

The number gets coerced to a string, then concatenated.

Other operators (-, *, /, etc.) don’t have this ambiguity — they always coerce to numbers:

console.log("2" - 0); // 2 (number)
console.log("2" * 2); // 4 (number)

---

Best practices to avoid surprises

1. Be explicit about types before operations

// Explicit numeric conversion
let sum = Number("2") + 2;
console.log(sum); // 4

// Explicit string conversion
let concat = String(2) + "2";
console.log(concat); // "22"

2. Prefer strict equality (===)

console.log(2 === "2"); // false
console.log(2 == "2");  // true (coercion happens)

3. Use linting / tooling
   Enable ESLint with rules like eqeqeq and no-implicit-coercion — they’ll catch these cases automatically.

4. Avoid relying on implicit coercion
   Being explicit with conversions keeps your code safer and easier to maintain.

---

TL;DR: Explicitly cast when mixing numbers and strings, and use === for comparisons. That way you avoid JavaScript’s automatic coercion pitfalls.

---

[mirkashi]

Really appreciate the clear explanation. Now I understand why + behaves differently with strings and numbers. I’ll make sure to use explicit casting to avoid these issues.