JavaScript Interview Questions
  • JavaScript Interview Questions
  • Contact
  • Introduction
  • Question 1
  • Question 2
  • Question 3
  • Question 4
  • Question 5
  • Question 6
  • Question 7
  • Question 8
  • Question 9
  • Question 10
  • Question 11
  • Question 12
  • Question 13
  • Question 14
  • Question 15
  • Question 16
  • Question 17
  • Question 18
  • Question 19
  • Question 20
  • Question 21
  • Question 22
  • Question 23
  • Question 24
  • Question 25
  • Question 26
  • Question 27
  • Question 28
  • Question 29
  • Question 30
  • Question 31
  • Question 32
  • Question 33
  • Question 34
  • Question 35
  • Question 36
  • Question 37
  • Question 38
  • Question 39
  • Question 40
  • Question 41
  • Question 42
  • Question 43
  • Question 44
  • Question 45
  • Question 46
  • Question 47
  • Question 48
  • Question 49
  • Question 50
  • Question 51
  • Question 52
  • Question 53
  • Question 54
  • Question 55
  • Question 56
  • Question 57
  • Question 58
  • Question 59
  • Question 60
  • Question 61
  • Question 62
  • Question 63
  • Question 64
  • Question 65
  • Question 66
  • Question 67
  • Question 68
  • Question 69
  • Question 70
  • Question 71
  • Question 72
  • Question 73
  • Question 74
  • Question 75
  • Question 76
  • Question 77
  • Question 78
  • Question 79
  • Question 80
  • Question 81
  • Question 82
  • Question 83
  • Question 84
  • Question 85
  • Question 86
  • Question 87
  • Question 88
  • Question 89
  • Question 90
  • Question 91
  • Question 92
  • Question 93
  • Question 94
  • Question 95
  • Question 96
  • Question 97
  • Question 98
  • Question 99
  • Question 100
  • Epilogue
Powered by GitBook
On this page
  • Question
  • Answer

Question 32

Question

Can you explain how to use Symbols as private properties in ES6 classes?

Answer

Symbols are perfect for creating private properties within ES6 classes. Here's a breakdown of how they work:

The Problem with Traditional Private Properties:

  • No True Privacy: In plain JavaScript, methods like _property (using an underscore prefix) aren't truly private. They can be accessed and modified from outside the class if someone really tries.

  • Limited Encapsulation: This lack of strong privacy makes it harder to maintain code integrity and enforce intended behavior.

Symbols to the Rescue!

  • Unique Identifiers: Symbols create unique, non-enumerable keys that are ideal for private properties. Since they're not part of the standard object enumeration, they're hidden from casual inspection.

  • Symbol() Function: Use Symbol() to generate a new symbol.

Example Implementation:

class BankAccount {
  constructor(initialBalance) {
    this[Symbol('balance')] = initialBalance; // Using Symbol as the key
  }

  deposit(amount) {
    this[Symbol('balance')] += amount;
  }

  withdraw(amount) {
    if (this[Symbol('balance')] >= amount) {
      this[Symbol('balance')] -= amount;
      return true; // Success
    } else {
      return false; // Insufficient funds
    }
  }

  getBalance() {
    return this[Symbol('balance')]; 
  }
}

// Create an account
const myAccount = new BankAccount(100);

// Deposit and withdraw
myAccount.deposit(50);
console.log(myAccount.getBalance()); // Accessing the balance directly is harder

// Can't access directly through `myAccount.balance` or similar

Explanation:

  1. Symbol as Key: We use Symbol('balance') to create a unique symbol key. This becomes our private property identifier.

  2. Setting and Accessing Values: Inside the class constructor, we assign an initial balance using this symbol key. When we need to get or modify the balance later (e.g., in deposit, withdraw, or getBalance), we access it through the same symbol key.

Benefits:

  • Strong Privacy: Symbols make it much harder for external code to directly manipulate private properties, protecting your class's internal state.

  • Improved Encapsulation: Private properties reinforce the principles of encapsulation, making your classes more robust and maintainable.

PreviousQuestion 31NextQuestion 33

Last updated 9 months ago