Build the solution · 3 / 5

Require useful package measurements

Describe a delivery with at least one positive package weight.

YOUR TASK

Make this happen

3 steps

Add required packages: a nonempty array of objects, each requiring positive numeric weightKg and rejecting extra fields.
Keep the working capabilities from the previous lesson and connect the new pieces to the same solution.
Check the complete solution, then inspect any unmet requirements.

THE IDEA BEHIND IT

What this step adds

Add required packages: a nonempty array of objects, each requiring positive numeric weightKg and rejecting extra fields.

Files to work in

contract.json. Other files are the working baseline. New files include named resource skeletons and TODO guidance. Complete their fields and connect them using the objectives, schema completion and reference guide.

Validate where the value lives

Array limits apply to packages; numeric constraints belong to each item’s weightKg. A requirement on a parent object does not automatically require child fields.

Host-specific schema capabilities

Integration configuration, workflow inputs and workspace handlers each accept their own schema subset and annotations. Importing this external JSON Schema does not activate UI annotations in every host.

Local IaC input checks and lesson contracts do not replace platform JSON Schema/OpenAPI processing. No external references, uploads or embeddings run here.

Files to change: contract.json

What you’re building: Define a reliable supplier delivery contract, then make its API discoverable.

This step starts with the earlier solution and one new challenge. Each lesson keeps its own draft.

Read the starter files

main.cococo

external_schema "supplier" {
  name = "Supplier delivery contract"
  format = "JSON_SCHEMA"
  sourceText = file("contract.json")
}

contract.json

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "title": "Supplier delivery",
  "type": "object",
  "properties": {
    "trackingId": {
      "type": "string",
      "minLength": 1
    },
    "status": {
      "type": "string",
      "enum": [
        "dispatched",
        "delivered"
      ],
      "default": "dispatched"
    }
  },
  "required": [
    "trackingId"
  ],
  "additionalProperties": false
}

Reference: schemas · authoring schemas · external-schemas