Most effective method for converting a table of data to TypeScript

Question

Most effective method for converting a table of data to TypeScript

Searching for an effective method to map a table of enum (or interface) data to the correct location.

https://i.sstatic.net/5hF2q.png

For instance, Smoke Sensor - Push Button can only be linked to SS - PI SYMBOL and Smoke Sensor - PushButton can only be associated with 000 - TTT PARAMETER.

I hope you understand what I mean.

How do I establish these mappings?

Updated:

I am attempting to achieve this using TypeScript:

export enum IName {
  SmokeSensor = 'SmokeSensor',
  GasSensor = 'GasSensor',
  MotionSensor = 'MotionSensor',
  WindowSensor = 'WindowSensor',
  Sensor = 'Sensor',
  PushButton = 'PushButton',
  Switch = 'Switch',
  Temperature = 'Temperature',
}

export enum ISymbol {
  SS = 'SS',
  SG = 'SG',
  SM = 'SM',
  SW = 'SW',
  SE = 'SE',
  PI = 'PI',
  SI = 'SI',
  TI = 'TI',
}

export enum IParameter {
  TTT = 'TTT',
  OOO = '000',
  OFF = 'OFF',
  OON = 'OON',
  POS = '0',
  NEG = '1',
}

interface IActivateSensors {
  name: Omit<IName, 'Switch' & 'Temperature'>
  symbol: Omit<ISymbol, 'SI' & 'TI'>
  parameter: Pick<IParameter, 'TTT' & '000'>
}

interface ISwitchSensor {
  name: IName.Switch
  symbol: ISymbol.SI
  parameter: Pick<IParameter, 'OFF' & 'OON'>
}

interface ITemperatureSensor {
  name: IName.Temperature
  symbol: Omit<ISymbol, 'SI' & 'TI'>
  parameter: Pick<IParameter, 'TTT' & '000'>
}

export type Sensors = IActivateSensors | ITemperatureSensor | ISwitchSensor

However, there may be a more efficient way to accomplish this.

javascript typescript

Answer 1

Answer №1

If you grasp the concept, you can implement it in the following way:

export enum Name {
    SmokeSensor = 'SS',
    GasSensor = 'SG',
    MotionSensor = 'SM',
    WindowSensor = 'SW',
    Sensor = 'SE',
    PushSensor = 'PI',
    Switch = 'SI'
}

export interface Symbol {
    [Name.SmokeSensor]: ParameterRange;
    [Name.GasSensor]: ParameterRange;
    [Name.MotionSensor]: ParameterRange;
    [Name.WindowSensor]: ParameterRange;
    [Name.Sensor]: ParameterRange;
    [Name.PushSensor]: ParameterRange;
    [Name.Switch]: ParameterOnOff;
}

export type ParameterRange = '000' | 'TTT'; // and more
export type ParameterOnOff = 'OFF' | 'OON';

function doStuff<N extends Name>(name: N, parameter: Symbol[N]) {
    // actions
}

However, mapping all values for 000 - TTT is required as they likely represent a range of values.

Edit 1

A potential solution could involve creating constants:

const ParameterRange = {
    '000': '000',
    'TTT': 'TTT'
    // additional values
}

const ParameterOnOff = {
    'OFF': 'OFF',
    'OON': 'OON'
}

export const Values = {
    SmokeSensor: { Symbol: { SS: 'SS' }, Parameter: ParameterRange },
    GasSensor: { Symbol: { SG: 'SG' }, Parameter: ParameterRange },
    MotionSensor: { Symbol: { SM: 'SM' }, Parameter: ParameterRange },
    WindowSensor: { Symbol: { SW: 'SW' }, Parameter: ParameterRange },
    Sensor: { Symbol: { SE: 'SE' }, Parameter: ParameterRange },
    PushSensor: { Symbol: { PI: 'PI' }, Parameter: ParameterRange },
    Switch: { Symbol: { SI: 'SI' }, Parameter: ParameterOnOff }
}

Values.SmokeSensor.Symbol.SS;
Values.Switch.Parameter.OFF;

This approach enforces mapping every value within ParameterRange, eliminating the need for value checks.

Edit 2

Can this be achieved using your enum like so?

type TActivateSensors = { [Name in Exclude<IName, IName.Switch | IName.Temperature>]: { Symbol: Exclude<ISymbol, ISymbol.SI | ISymbol.TI>; Parameter: Extract<IParameter, IParameter.TTT | IParameter.OOO>; } }
type TSwitchSensor = { [Name in Extract<IName, IName.Switch>]: { Symbol: Extract<ISymbol, ISymbol.SI>; Parameter: Extract<IParameter, IParameter.OFF | IParameter.OON>; } }
type TSensors = TActivateSensors & TSwitchSensor;

export type Sensor<Name extends keyof TSensors> = {
    name: Name;
    symbol: TSensors[Name]['Symbol'];
    parameter: TSensors[Name]['Parameter'];
};

const sensor: Sensor<IName.Switch> = {
    name: IName.Switch,
    symbol: ISymbol.SI,
    parameter: IParameter.OFF
}

By utilizing type Sensor on an object, TypeScript mandates the use of allowed enums for each property.

Answer 2

If you grasp the concept, you can implement it in the following way:

export enum Name {
    SmokeSensor = 'SS',
    GasSensor = 'SG',
    MotionSensor = 'SM',
    WindowSensor = 'SW',
    Sensor = 'SE',
    PushSensor = 'PI',
    Switch = 'SI'
}

export interface Symbol {
    [Name.SmokeSensor]: ParameterRange;
    [Name.GasSensor]: ParameterRange;
    [Name.MotionSensor]: ParameterRange;
    [Name.WindowSensor]: ParameterRange;
    [Name.Sensor]: ParameterRange;
    [Name.PushSensor]: ParameterRange;
    [Name.Switch]: ParameterOnOff;
}

export type ParameterRange = '000' | 'TTT'; // and more
export type ParameterOnOff = 'OFF' | 'OON';

function doStuff<N extends Name>(name: N, parameter: Symbol[N]) {
    // actions
}

However, mapping all values for 000 - TTT is required as they likely represent a range of values.

Edit 1

A potential solution could involve creating constants:

const ParameterRange = {
    '000': '000',
    'TTT': 'TTT'
    // additional values
}

const ParameterOnOff = {
    'OFF': 'OFF',
    'OON': 'OON'
}

export const Values = {
    SmokeSensor: { Symbol: { SS: 'SS' }, Parameter: ParameterRange },
    GasSensor: { Symbol: { SG: 'SG' }, Parameter: ParameterRange },
    MotionSensor: { Symbol: { SM: 'SM' }, Parameter: ParameterRange },
    WindowSensor: { Symbol: { SW: 'SW' }, Parameter: ParameterRange },
    Sensor: { Symbol: { SE: 'SE' }, Parameter: ParameterRange },
    PushSensor: { Symbol: { PI: 'PI' }, Parameter: ParameterRange },
    Switch: { Symbol: { SI: 'SI' }, Parameter: ParameterOnOff }
}

Values.SmokeSensor.Symbol.SS;
Values.Switch.Parameter.OFF;

This approach enforces mapping every value within ParameterRange, eliminating the need for value checks.

Edit 2

Can this be achieved using your enum like so?

type TActivateSensors = { [Name in Exclude<IName, IName.Switch | IName.Temperature>]: { Symbol: Exclude<ISymbol, ISymbol.SI | ISymbol.TI>; Parameter: Extract<IParameter, IParameter.TTT | IParameter.OOO>; } }
type TSwitchSensor = { [Name in Extract<IName, IName.Switch>]: { Symbol: Extract<ISymbol, ISymbol.SI>; Parameter: Extract<IParameter, IParameter.OFF | IParameter.OON>; } }
type TSensors = TActivateSensors & TSwitchSensor;

export type Sensor<Name extends keyof TSensors> = {
    name: Name;
    symbol: TSensors[Name]['Symbol'];
    parameter: TSensors[Name]['Parameter'];
};

const sensor: Sensor<IName.Switch> = {
    name: IName.Switch,
    symbol: ISymbol.SI,
    parameter: IParameter.OFF
}

By utilizing type Sensor on an object, TypeScript mandates the use of allowed enums for each property.

Most effective method for converting a table of data to TypeScript

Answer №1

Edit 1

Edit 2

Similar questions

Leveraging useContext to alter the state of a React component

Is it possible to extract elements from a single list and insert them onto various pages?

Sorting JSON data using JQuery Ajax

The font size varies depending on the language being used

Is it possible to utilize the existing class elements as an array identifier?

Assigning event to the body element

Display the dropdown selected value within a Laravel Blade template

What is the process for inputting data into a Inertia component?

How to Properly Initialize a Variable for Future Use in a Component?

Calculating date discrepancies with JavaScript

WebStorm disregards tsconfig compiler directives when working with Angular applications

Tips for sequentially calling multiple await functions within a for loop in Node.js when one await is dependent on the data from another await

I'm curious about why I'm receiving the error "Unable to bind to 'ngFor' since it is not recognized as a property of 'li'. Can someone please explain why this is happening?

Utilizing the String Enum for mapping an interface with an index

``Are you experiencing trouble with form fields not being marked as dirty when submitting? This issue can be solved with React-H

Where did my HTML5 Canvas Text disappear to?

How can I efficiently iterate through the array of index IDs and then iterate individually through the communes, categories, and locations?

How can we eliminate all elements from jQuery except for the first and second elements?

Combine the array elements by date in Angular, ensuring no duplicates are present

Issue with a hidden div, problem with scrolling, a div overlapping other divs