Wire a typed callback — Review and demonstrate

PART I

Warm-up

Reconnect with a useful idea before starting wire a typed callback. In one or two sentences, describe the input, output or host boundary from the previous exercise that this lesson builds on. If you are arriving directly, skim the worked example first; there is no locked prerequisite.

A rough note is enough. You can revise it after the example.

PART II

Instruction & guided example

Review a complete callback contract

A callback has an input and result contract. A callback is a callable value installed for a later invocation. Read its parameter list and return type before its body. A no-argument fnc() -> void does not receive an Event merely because its registration sits inside events. If the host supplies an event payload, it must state the payload shape and callback signature.

A proposed support callback says “receives a request and handles it.” Review inputs are requestId:string, body:string, ownerWindow:string; result void; effects queue one permitted request and show Queued after confirmation.

Separate configuration-time values from delivery-time inputs. For each invocation, list the actual input fields, the values read, and the promised result. An undeclared field or wrong type is a contract mismatch, not an invitation to guess a host conversion. Worked case: A complete review separates fields, owner, permission, effect and completion evidence. A requestId identifies a request; it does not prove queue insertion. Showing Queued is justified only by the supplied confirmation rule.

Compare the tempting alternative: Inferring success from entering the callback skips the only evidence that the effect completed. Leaving ownerWindow unspecified permits late updates to the wrong view.

Worked reasoning and supplied artifact

// Paper trace / supplied exercise-host contract; no execution claimed.
// A proposed support callback says “receives a request and handles it.” Review inputs are requestId:string, body:string, ownerWindow:string; result void; effects queue one permitted request and show Queued after confirmation.
// A complete review separates fields, owner, permission, effect and completion evidence. A requestId identifies a request; it does not prove queue insertion. Showing Queued is justified only by the supplied confirmation rule.

Illustrative example from the proposed WillowScript design. The language and WUIX/WMATH/WDB/WAUDIO/WTMP services are not implemented in the supplied source. This site has no interpreter, VM or native host and does not execute or certify the snippet.

Try the guided change

Reconstruct the supplied worked case first: list its inputs, intermediate decisions and final artifact. Compare each row with the explanation and identify exactly where the rejected alternative fails. Then use the changed inputs in Part IV for independent work.

• Write the supplied inputs and initial state before following the example.
• Reconstruct each intermediate calculation or host decision, then compare with the worked artifact.
• Explain why the contrasting alternative fails before attempting the changed inputs in Part IV.

PART III

Take a breather

Step back after the guided example. Look away from the screen, stretch, or reread your prediction. This is an optional learning pause, not a timer or an assessment gate.

When you return, try to name the lesson’s key idea without copying its wording. If that feels difficult, return to Part II and trace one line rather than restarting the entire lesson.

PART IV

Independent practice

Project context: Support request workflow. Build a small, understandable change around wire a typed callback.

Rewrite the vague description as a contract and trace confirmed queueing versus rejected permission.

What to produce

A contract with input/result/effect/owner/evidence columns and two traces.

• State the intended behavior in a sentence before editing.
• Use only source-backed syntax and the host services whose contract you have been given.
• Record a normal case and a boundary or unavailable-resource case.
• Label hand predictions separately from anything actually measured in a supplied toolchain.

Syntax colors are a reading aid, not a compiler. The line you are editing stays uncolored until you move to a different line; capitalization is never changed. Drafts stay on this browser and code is not executed.

import wuix.widget;
import app;
domain Workspace {
    const application = Application({
        name: "Workspace",
        window: { title: "Dashboard", size: [1280, 800] },
        events: {
            "app.ready": fnc() -> void { console.log("Ready"); }
        }
    });
}

PART V

Self-check

Use this check to notice what to revisit. It does not award a private course grade, block another page or claim to verify compiled code. Every answer has a learning explanation.

You may keep exploring even if you are unsure. Use the hint, compare the trace, and revise your explanation.

PART VI

Recap & small task

Bring the idea back to the mod feature you are building. A useful recap connects the mechanism to a decision you can make in your own code.

• Review a complete callback contract
• Rewrite the vague description as a contract and trace confirmed queueing versus rejected permission.
• Separate source-backed behavior, host requirements and untested predictions.

One small recap task

Replace the word handles with one observable effect.

This marks your personal practice record only. It is not a certification or an official workspace assessment.