Skip to content
Mapper

Design Principles

Mapper is built around a small number of rules.

Explicit mapping over guessing

Section titled “Explicit mapping over guessing”

The user decides what each external column means.

Source columns are positional

Section titled “Source columns are positional”
source identity = column index

No unnecessary generated source identifiers.

Target fields have stable identity

Section titled “Target fields have stable identity”
target identity = generated field ID

Renaming display labels does not change runtime identity.

Mapping is portable

Section titled “Mapping is portable”

The graph UI produces a small language-neutral specification.

Frontend
→ MappingSpec
→ Go backend SDK (generated TypeScript models for the frontend)

File transport is replaceable

Section titled “File transport is replaceable”
multipart
TUS
custom upload

all converge to a completed:

FileID

Business processing belongs to the application

Section titled “Business processing belongs to the application”

Mapper transforms records.

Your application decides what to do with them.