Is it beneficial to utilize an interface for constructing a class model?

Question

Is it beneficial to utilize an interface for constructing a class model?

The Interface:

export interface IAddEditGeneralDictionary {
      Code: string;
      StartDate?: Date | string;
      FinishDate?: Date | string;
      Name: string;
    }

The Realization:

export class AddEditGeneralDictionary implements IAddEditGeneralDictionary {
  constructor(public Code: string,
    public StartDate: Date | string,
    public FinishDate: Date | string,
    public Name: string){
}

My attempt to make properties private and utilize set/get was hindered by the restrictions of the interface.

What are your thoughts on using an interface to construct a model class?

typescript typescript2.0

Answer 1

Answer №1

An interface serves as a shared boundary allowing different components/entities to communicate effectively. It must be public so that users have visibility into what they can expect when interacting with a concrete class through the interface.

Any private properties or methods are considered implementation details and should be handled within the concrete class itself.

For instance

interface Vehicle {
  start(): void;
}

class Car implements Vehicle {
  private engine;
  private wheels;
  public start(): void {}
}

class Jet implements Vehicle {
  private engine;
  private airframe;
  public start(): void {}
}

While implementations have the flexibility to define private properties, these properties are not particularly useful in an interface context.

Answer 2

An interface serves as a shared boundary allowing different components/entities to communicate effectively. It must be public so that users have visibility into what they can expect when interacting with a concrete class through the interface.

Any private properties or methods are considered implementation details and should be handled within the concrete class itself.

For instance

interface Vehicle {
  start(): void;
}

class Car implements Vehicle {
  private engine;
  private wheels;
  public start(): void {}
}

class Jet implements Vehicle {
  private engine;
  private airframe;
  public start(): void {}
}

While implementations have the flexibility to define private properties, these properties are not particularly useful in an interface context.

Is it beneficial to utilize an interface for constructing a class model?

Answer №1

Similar questions

TS1316 Error: You can only have global module exports at the top level of the file

How can I remove specific items from a PrimeNG PickList?

When the variable type is an interface, should generics be included in the implementation of the constructor?

Expanding a class in Angular 2

What is the best way to include text or a label on my Angular map without using a marker?

Select characteristics with designated attribute types

Diverse Range of Exports Available in React Component Library

Whenever I make a POST request to the API in Ionic 2, I encounter a "Connection refused (x192)" error

The length of Array(n) is incorrect when running on production in Next.js

Is there a way to adjust the height of mat-sidenav-content to be 100%?

Unraveling TypeScript code expressions

Prevent the event listener from continuously triggering

In JavaScript, the function will return a different object if the string in an array matches the

Issues arise when trying to update the modelValue in unit tests for Vue3 Composition API

Tips for directing your attention to an input field in Angular

TypeScript error: Attempting to utilize an argument of type 'any[]' that cannot be assigned to a parameter of type 'SetStateAction<never[]>'

Tips for overlaying a webpage with several Angular components using an element for disabling user interactions

Calculate the difference and sum of time values with varying signs in JavaScript

Having trouble closing my toggle and experiencing issues with the transition not functioning properly

Troubleshooting Angular MIME problems with Microsoft Edge