JS Data Privacy

#discuss #javascript

Hello again 👋

I’ve been grinding in the lab trying get a deeper understanding of Javascript. I’m currently working on a tiny project utilizing some ES6 features. I noticed while creating some classes that instance variables don’t seem to have much protection from outside interference. I would like to hear from other devs on how they go about protecting their instance data in production or if that’s even a valid issue?

Top comments (3)

Avalander • Feb 27 '20

I don't really use classes with Javascript. You can encapsulate private data with closures though.

const Unicorn = name => {
  let level = 0

  return {
    name() {
      return name
    },
    level() {
      return level
    },
    levelUp() {
      level += 1
      return this
    },
  }
}

const twilight = Unicorn('Twilight Sparkle')

twilight.name()    // 'Twilght Sparkle'
twilight.level()   // 0
twilight.levelUp()
twilight.level()   // 1

Slick3gz • Feb 27 '20

Earlier in Jonas Schmedtmann’s JS course he explained that IIFEs and closures could let you pick what you would like to expose to the public. I also read a post by Eric Elliot discussing classes vs function constructors vs factory functions, in which he advocated for the use of factory functions over the other two options for future flexibility. Just wondering if this is how most devs approach this “problem”.

Slick3gz • Feb 27 '20

Do you use TypeScript by itself or use it mainly for a framework? I recently picked up a course on Udemy from Stephen Grider that teaches using TypeScript with Angular.

DEV Community

JS Data Privacy

Top comments (3)

Read next

Node.js as a normal script.js file

Project: Build a Weather App Using JavaScript and a Weather API

Apply CSS in Next.js with StayedCSS

Funny-Captcha Web