Core Type Mapping

Core Type Mapping Guide

Overview

This guide provides the mapping between OpenAPI string formats and their corresponding TypeScript type classes for use in Tasks 5, 7, 8, and 9.

🚨 Critical Usage Rules

• Task 5: Use these mappings when creating OpenAPI specifications - set the correct format field
• Task 7: Use these mappings in data transformation and validation
• Task 8 & 9: Use these mappings for type assertions in tests (e.g., instanceof Email, instanceof UUID)
• String Conversion: All types support .toString() method and template literal interpolation
• Import Sources: Import types from the specified packages, not from Node.js built-ins

AWS Types (@auditmation/types-amazon-js)

Microsoft Azure Types (@auditmation/types-microsoft-js)

Google Cloud Types (@auditmation/types-google-js)

Core Types (@auditmation/types-core-js)

Binary/Encoding

Networking

Date/Time

Numeric

Communication/Identity

Identifiers

Security

Geographic

File/Media

Business/Domain

Complete Type Mapping Reference Table

Consolidated Quick Reference

Usage Patterns by Task

Task 5: OpenAPI Specification

# Use format field to specify type
properties:
  id:
    type: string
    format: uuid  # → Will generate UUID type
  email:
    type: string
    format: email  # → Will generate Email type
  createdAt:
    type: string
    format: date-time  # → Will generate Date type

Task 7: Implementation (Mappers)

import { map, toEnum } from '@auditmation/util-hub-module-utils';
import { UUID, Email, URL } from '@auditmation/types-core-js';  // NEVER from Node.js!

export function toUserInfo(raw: any): UserInfo {
  return {
    id: map(UUID, raw.id),
    email: map(Email, raw.email),
    website: map(URL, raw.website_url),
    createdAt: map(Date, raw.created_at),
    status: toEnum(StatusEnum, raw.status)
  };
}

Task 8 & 9: Testing

import { UUID, Email } from '@auditmation/types-core-js';

it('should return user with correct types', () => {
  const user = await getUser('123');

  expect(user.id).to.be.instanceof(UUID);
  expect(user.email).to.be.instanceof(Email);
  expect(user.createdAt).to.be.instanceof(Date);
});

String Conversion Support

All custom types support string conversion:

const email = new Email('user@example.com');

// Direct toString()
const emailString = email.toString();  // "user@example.com"

// Template literal (automatic conversion)
const message = `User email: ${email}`;  // "User email: user@example.com"

// JSON serialization
JSON.stringify({ email });  // {"email":"user@example.com"}

Package Import Requirements

Required Dependencies

{
  "dependencies": {
    "@auditmation/types-core-js": "*",
    "@auditmation/util-hub-module-utils": "*"
  },
  "devDependencies": {
    "@auditmation/types-amazon-js": "*",  // If using AWS
    "@auditmation/types-microsoft-js": "*",  // If using Azure
    "@auditmation/types-google-js": "*"  // If using GCP
  }
}

Common Mistakes to Avoid

❌ WRONG - Using Node.js built-ins

import { URL } from 'url';  // WRONG!
import { URL } from 'node:url';  // WRONG!

✅ CORRECT - Using core types

import { URL } from '@auditmation/types-core-js';  // CORRECT!

❌ WRONG - Direct enum instantiation

const status = new StatusEnum('active');  // WRONG - constructor is private!

✅ CORRECT - Using toEnum

const status = toEnum(StatusEnum, 'active');  // CORRECT!

❌ WRONG - Manual type conversion

const uuid = raw.id as UUID;  // WRONG - no validation!

✅ CORRECT - Using map function

const uuid = map(UUID, raw.id);  // CORRECT - validates and converts!

Priority Rules

1. Always use core types over native JavaScript types when available
2. Import from correct package - never from Node.js built-ins
3. Use map() for type conversion - provides validation
4. Use toEnum() for enums - never instantiate directly
5. All types support .toString() - use for string conversion

Web/Protocol

Versioning

Misc

Usage Patterns

Task 5: OpenAPI Specification

properties:
  email_address:
    type: string
    format: email  # Maps to Email type
  website_url:
    type: string
    format: url    # Maps to URL type
  user_id:
    type: string
    format: uuid   # Maps to UUID type

Task 7: Data Transformation

import { Email, URL, UUID } from '@auditmation/types-core-js';
import { map } from '@auditmation/util-hub-module-utils';

function mapUser(raw: any): User {
  return {
    id: map(UUID, raw.user_id),
    email: map(Email, raw.email_address),
    website: map(URL, raw.website_url)
  };
}

Task 8 & 9: Test Assertions

import { Email, URL, UUID } from '@auditmation/types-core-js';

// Test assertions
expect(user.id).to.be.instanceof(UUID);
expect(user.email).to.be.instanceof(Email);
expect(user.website).to.be.instanceof(URL);

String Conversion Examples

// All types support toString() and template literals
const email = new Email('user@example.com');
const emailString = email.toString();
const message = `User email: ${email}`;

const uuid = new UUID('123e4567-e89b-12d3-a456-426614174000');
const uuidString = uuid.toString();
const log = `Processing user ${uuid}`;

Package Import Requirements

🚨 CRITICAL: Always import from the specified packages:

// Core types - ALWAYS import from @auditmation/types-core-js
import { URL, UUID, Email, IpAddress } from '@auditmation/types-core-js';

// AWS types
import { Arn, AwsService } from '@auditmation/types-amazon-js';

// Azure types  
import { AzureVmSize, AzureResource } from '@auditmation/types-microsoft-js';

// Google Cloud types
import { GcpAccessPolicy } from '@auditmation/types-google-js';

// NEVER import URL from Node.js built-ins
// ❌ import { URL } from 'url';  // WRONG
// ✅ import { URL } from '@auditmation/types-core-js';  // CORRECT

Validation and Error Handling

All typed values can be validated and will throw appropriate errors for invalid formats:

try {
  const email = new Email('invalid-email');  // Throws validation error
} catch (error) {
  // Handle validation error
}

// Safe validation with try-catch in mappers
function safeMapEmail(raw: string): Email | null {
  try {
    return new Email(raw);
  } catch {
    return null;  // Or handle as appropriate for your use case
  }
}