Factory (Pattern) — JS: Polymorphism

Using subtype polymorphism doesn't remove conditional constructs, except in some dispatching cases, such as by key or filename.

More often, the conditional construct is left alone only. When we select a suitable implementation, we use it within the polymorphic function directly, without conditions.

In the previous lesson, we looked at an example function that selects the desired way of implementing the strategy based on the user's age and returns it:

const chooseCostInsuranceStrategy = (user) => {
  if (user.getAge() < 18) {
    return new LessThan18();
  } else if (/* ... */) {
    // Some code
  }
}

Here we see a function that selects the desired class, creates the object, and then returns it. Programmers call it a factory method. We can implement a factory in any way, including all the methods we've learned in this course.

Generally, we can call a factory anything that creates an object. It doesn't have to use different classes — there could be only one class. But the creation process involves some preliminary calculations. In real projects, factories can be quite large.

We often implement factories as classes with a static method called factory.

Factories themselves don't make objects because it's not an abstraction of data, and it makes no sense to substitute them. Otherwise, you'll get substitutes for substitutes:

export default class {
  static factory(/* parameters */) {
    // Factory code
  }
}

Class dispatch

JavaScript allows you to create objects using a class reference:

const className = Application;
const app = new className();

This syntax gives you great scope for dispatching. For example, in some cases, it'll be possible to get away from the conditional structures completely:

import ManagerPolicy from './policies/ManagerPolicy.js';
import WorkerPolicy from './policies/WorkerPolicy.js';

// Policy — we use this name for authorization (by the system for checking access rights)
const mapping = {
  manager: ManagerPolicy,
  worker: WorkerPolicy,
};

const getUserPolicy = (user) => {
  const className = mapping[user.getType()];
  return new className();
};

---

Are there any more questions? Ask them in the Discussion section.

The Hexlet support team or other students will answer you.

About Hexlet learning process

• Article “How to Learn and Cope with Negative Thoughts“
• Article “Learning Traps“
• Article “Complex and simple programming tasks“