Import only the public APIs you use — Flash-check repair

PART I

Warm-up

Reconnect with a useful idea before starting import only the public apis you use. 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

Repair a dependency claim that promises sibling APIs

An import requests a named public API from the proposed library hierarchy. A narrow import is not evidence that sibling modules are visible, that native services are installed or that a capability is granted. Existing Willow module experience helps you ask precise questions, but it cannot fill missing WillowScript host contracts.

The broken architecture note says importing wuix.widget.button makes WAUDIO playback available. The sample repair keeps the button import scoped to its documented API, lists audio as a separate proposed library contract and removes the unsupported playback claim. No code execution is needed to see that unrelated library availability was assumed without evidence.

Do not replace the claim with a guessed audio module path. Use source-named WAUDIO capabilities and request its supplied API contract before authoring a concrete integration. A correction can be a precise dependency requirement rather than a fabricated import.

Worked reasoning and supplied artifact

// Worked contract artifact:
// The broken architecture note says importing wuix.widget.button makes WAUDIO playback available. The sample repair keeps the button import scoped to its documented API, lists audio as a separate proposed library contract and removes the unsupported playback claim. No code execution is needed to see that unrelated library availability was assumed without evidence.

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

Rewrite the broken note into known button scope, separate audio need and pending service contract.

• 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: Shared pricing rules. Build a small, understandable change around import only the public apis you use.

Repair a design note asserting that wdb automatically provides WTMP cache creation. Separate query responsibilities from temporary-storage requirements and name what must be supplied.

What to produce

A corrected dependency map and explicit missing temporary-storage API contract.

• 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.

fnc add(a: i32, b: i32) -> i32 {
    return a + b;
}
fnc main() -> i32 {
    return add(2, 3);
}

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.

• Repair a dependency claim that promises sibling APIs
• Rewrite the broken note into known button scope, separate audio need and pending service contract.
• Separate source-backed behavior, host requirements and untested predictions.

One small recap task

Rewrite the broken note into known button scope, separate audio need and pending service contract.

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