Skip to content

dev(refactor): Design pattern #77

@Cyber-Syntax

Description

@Cyber-Syntax

What is the exact problem?

I am frustrated to update classes over and over again for the new features or fixes.

Which design pattern would be better?

Cretional design patterns

  • Abstract Factory
  • Factory
    • We already uses this on some part of classes.
  • Builder
  • Singleton
  • Prototype

Structural design patterns

  • Adapter
  • Bridge
  • Composite
  • Decorator
  • Facade
    • We already uses this on some part of classes.
  • Flyweight
  • Proxy

Behavioral design patterns

  • Chain of responsibility
  • Command design pattern
    • It is good for cli.
  • Iterator
  • Mediator
  • Memento
  • Observer
    • It would be useful for the updates notification?
  • State
  • Strategy
    • It would be great for verification strategies.
  • Template
  • Visitor

Is it overkill to use design pattern?

I am not trying to fit design pattern to my project, I am trying to solve the problem I encounter.
Therefore, I don't think it is overkill but it might be solution.

Others

Metadata

Metadata

Assignees

Projects

Status

In review

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions