The current garage door planner asks whether someone wants to replace, install, repair or get advice. It also asks for a door type and size. A future service intake could capture specific symptoms, but it shouldn’t turn a homeowner’s description into a component diagnosis behind the scenes.

Separate fields by who can verify them

A door stopping partway is an observation. An obstruction, alignment issue or component fault is a possible technical finding. Preserve their different origins even when they appear together in the same support dashboard. A public form should have its own accepted schema that contains only user-reported fields.

type Symptom = 'no-response' | 'stops-partway' | 'visible-damage' | 'other'; type PublicReport = { symptoms: Symptom[]; observedAt?: string }; type Inspection = { findings: string; recordedBy: string }; type RepairRecord = { report: PublicReport; inspection?: Inspection }; 

Test which interface can write which fields

This is a proposed model. A future public endpoint should validate its request at runtime and reject or deliberately strip an inspection object supplied by the browser. TypeScript alone offers no protection against arbitrary JSON. In a separate staff path, check permissions before accepting an inspection entry and preserve the original report for reference.

For the existing planner, complete Repair a door or opener with Not sure yet as door type. Confirm that the summary shows the selected intent, retains the uncertain door type and displays no component diagnosis. That browser check tests the current product boundary. The API tests belong with an actual collection implementation.

Model provenance through the output too. A staff summary might display a homeowner observation alongside a dated inspection, with separate labels. Tests should catch a rendering change that gives both the same label and implies both have been technically verified.

Perth Quotes garage door planner is the live preview. Online enquiries are closed.