Type-safe business object mapping: EDIFACT segments → TypeScript objects (and back)

[hello-ediflow]

Instead of manually parsing segments like BGM+220+PO-001 and accessing elements[1], I want typed business objects like order.documentNumber. How can I map between EDIFACT messages and domain objects?

[hello-ediflow]

EDIFlow's Business Object Mapping provides exactly this:

import { BusinessObjectMapper } from '@ediflow/core';

// Parse EDIFACT → EDIMessage
const message = parser.parse(edifactString);

// Map to typed business object
const mapper = new BusinessObjectMapper(messageStructure, 'camelCase');
const order = mapper.mapToBusinessObject(message);

// Now you have IntelliSense and type safety!
console.log(order.documentNumber);         // 'PO-001'
console.log(order.parties.buyer.id);       // GLN
console.log(order.lineItems[0].productId); // EAN code
console.log(order.lineItems[0].quantity);  // number

// Modify and map back
order.lineItems[0].quantity = 150;
const updatedMessage = mapper.mapFromBusinessObject(order, { /* options */ });

5 mapping strategies available: code, name, camelCase, snake_case, kebab-case.

This eliminates the "segment[2].elements[3]" pattern that makes EDI code unreadable. Your domain layer works with clean TypeScript objects, completely decoupled from the EDI wire format.