From eb77cb78d990651e275b73990e36acd459a5848b Mon Sep 17 00:00:00 2001
From: tactonbishop <tactonbishop@gmail.com>
Date: Fri, 24 Jun 2022 21:00:04 +0100
Subject: [PATCH] Last Sync: 2022-06-24 21:00:04

---
 Data_Structures/Patterns/Module_pattern.md | 73 ++++++++++++++++++++++
 1 file changed, 73 insertions(+)

diff --git a/Data_Structures/Patterns/Module_pattern.md b/Data_Structures/Patterns/Module_pattern.md
index e69de29..3d92a03 100644
--- a/Data_Structures/Patterns/Module_pattern.md
+++ b/Data_Structures/Patterns/Module_pattern.md
@@ -0,0 +1,73 @@
+---
+tags:
+  - Data_Structures
+  - patterns
+  - oop
+---
+
+# Module pattern 
+
+> Come back and compare this with learning from Node.js
+
+With the module design pattern we create encapsulation: the variables and functions (as methods) are kept private inside the module and cannot be overwritten. This design pattern is familiar from Node.js development: every package you import into your project and download from NPM is a module.
+
+Generally you will create the module as a class, import it and then instantiate a new instance. However for private development, you could just as well use an object and duplicate it with `Object.create`.
+
+## Example
+
+Here is an example of a simple module that returns the age of a person.
+
+```js
+export default class Age {
+  constructor(name, birthYear) {
+    this.name = name;
+    this.birthYear = birthYear;
+  }
+  currentYear() {
+    return new Date().getFullYear();
+  }
+  get age() {
+    return this.currentYear() - this.birthYear;
+  }
+}
+```
+
+```js
+const martha = new Age('Martha', 1997);
+console.log(martha.age) // 24 
+```
+
+## Controlling access
+
+In the example above, `aValue` could be edited in instantiations of the class. Given that modules should not be overwrittable, you could make it a private property on the class. The benefit of getters and setters is that they dictate what can be modified and retrieved from the module. So if you use `get` and `set`  you can prevent overwrites.
+
+## Object modules
+
+---
+
+If you want to use an object instead of a class, you have to take greater care to ensure that the objects are not overwritable. **Also you cannot use the `#` modifier to make properties private.** 
+
+- Use getters and setters for updating and retrieving values
+- Use `Object.seal` to prevent changes to the parent object
+- Instead of using getters and setters, for individual properties you can set `writable` to be `false` for properties that you don't want changed
+
+There are examples of each in the following:
+
+```jsx
+export const age = {
+  name: '',
+  birthYear: new Number(),
+  currentYear() {
+    return new Date().getFullYear();
+  },
+  get age() {
+    return this.currentYear() - this.birthYear;
+  },
+};
+
+Object.seal(age);
+Object.defineProperty(age, 'aValue', {
+  value: 6,
+  writable: false,
+});
+```
\ No newline at end of file