Skip to content
KramorDS
Switch light or dark

Components

Forms

Every control shares one surface: the same height, radius, border and focus ring. Labels are always visible, hints explain, and errors say how to fix the problem.

FieldInputSelectCheckboxRadioSwitch

Fields

Field wires the label, hint and error to the control with ids, so a screen reader announces all three together. Control borders meet 3:1 against every surface.
Field anatomy

The admin URL of the source store.

Use a number between 50 and 250.

Optional

Visible to everyone in this workspace.

Inputs and selects

Inputs take a leading icon or a trailing unit. Selects are native, so they work with every keyboard, screen reader and mobile picker, styled to match.
Variations
pts/s

Shopify cost points per second.

Read only. Generated when the tenant was created.

Checkboxes, radios and switches

Checkboxes collect independent options, radios pick one of a set, and switches apply a setting the moment they change. Their boundaries use the input token so they read at 3:1.
Choices
Conflict policy

When a destination record already exists.

Applies to the next dispatch.

Locked by the workspace owner.

Validation

Validate on submit, show every problem at once, move focus to the first invalid field and keep what the person typed. Messages say what to do, not what went wrong.

Information: Source stores are read-only

Kramor never writes to a source platform. Connectors throw a violation error on any attempt.

Stored as a secret reference. Never shown again.

API

Field uses a render function so the control receives its id, describedby and invalid state.
PropTypeDefaultDescription
labelstring–Visible label, always rendered.
hintstring–Helper text. Hidden while an error shows.
errorstring–Sets aria-invalid on the control and announces politely.
requiredbooleanfalseAdds the required attribute and a visual marker.
optionalbooleanfalseShows an Optional tag when most fields are required.
children(control) => ReactNode–Spread control onto Input, Select or Textarea.

Do

Keep labels visible above the control

The label stays put while typing, so the person never loses track of what the field wants.

Don't

Use the placeholder as the label

The hint disappears on the first keystroke and placeholder text is easy to mistake for a filled value.

Overview
Color
Typography
Space, shape and motion
Actions
Forms
Feedback
Data display
Navigation
Overlays
Portal shell
Status and lifecycle
Trust and safety
Template gallery
Overview screen
Connections screen
Studio screen
Validation screen
Recovery screen
Governance screen
Settings screen
Switch light or dark mode